Here you will find a list of tools used by the Pulsar team and information about them.
Cirrus CI is used for Pulsar's continuous integration as well as for building application binaries.
Codacy is used to scan committed code for any issues that may have been missed.
Currently though Codacy is only used on the following repositories:
Crowdin will be used for Pulsar's internationalization efforts but exact details on this are still pending.
While most repositories you can easily tell what Package Manager is being used by checking for a specific lock file, there are some execptions to this that should be noted.
- pulsar uses
yarnas its Package Manager. - pulsar-edit.github.io uses
pnpmas its Package Manager.
The package-backend currently uses DigitalOcean to host the PostgreSQL Pulsar Package Repositories data in the cloud.
Both the package-backend and package-frontend use Google App Engine to host the compute instance of these websites in the cloud.
Pulsar Dependency Tester is a GitHub action used to test changes of a core Pulsar Dependency if you need to determine how your core package dependency will run on the current version of the Pulsar Editor.
This GitHub Action is a direct Pulsar replacement of the previous Action to test Atom Dependencies Setup Atom.