Contributing

Both external contributors and snapcrafters use the same method to update a snap. The README of the snap's repository should provide more information in how to do this, but this page provides a short overview.

Getting your changes merged

1. Create a personal fork of the repository.
2. Update the code and push to your personal fork.
3. Create a PR and ask for a review from @reviewers. Feel free to ping people personally too. You need at least one positive review from a member.

Getting your changes published to the Snap Store

1. When the code is merged, the automatic build will push a release to the candidate channel and create a "Call for testing" issue in the repository.
2. Install the app in the candidate channel, and write a comment on the "Call for testing" issue to explain the results.
3. If the test was successful, one of the Snapcrafters will run the required command to promote the snap to stable.

[archived] Old automation using the Snap Store Build service

Some snaps still use the old automation. For those snaps, the publishing process is slightly different.

1. When the code is merged, the automatic build will push a release to the edge channel.
2. Create a “call for testing” on the forum and ask people to test the edge channel.
3. If those tests are successful, publish the release to the stable channel.