Once the PR has been merged into the stable branch, then on the next git mirror sync (every 4 hours), launchpad will trigger a build of the snap that gets published to the snap store into the candidate channel.Someone from the team will review the open PR and either merge it or start a discussion with you with additional changes or clarification needed.Once the snap build has completed, you can find the built snap (to test with) under "Artifacts". You can watch the progress of the snap build from your PR (Show all checks -> Details). Once you've opened the PR, it will automatically trigger the build-test action that will launch a build of the snap.When you feel they're ready for submitting to the main repository (stable branch), open up a pull request from your my-bugfix-branch to the ubuntu/stable branch.To make things a bit more intuitive, let's rename your fork's remote too (since "origin" is hardly descriptive): In addition to your fork, you need to also add this remote repository.
Fork the repository into your own GitHub namespace.If this is your first time contributing to this snap, then there are a couple of things you need to do as a one-time setup to get ready to submit your first pull request: Here is the workflow for submitting a change to the stable branch, and getting it published in the snap store in the candidate channel.
#UBUNTU FONT VIEWER HOW TO#
How to contribute to this snap Initial setup And then once the PR has been merged the GitHub action will launch a build on launchpad that will be automatically uploaded to the snap store, in the candidate channel, for more extensive testing. Once the pull request has been submitted, there is a GitHub action that will automatically launch a build of the snap that you can use for testing.
The general workflow will be to submit PRs from your fork onto the "stable" branch. Here's the gnome-font-viewer badge links for example:īelow you will find some instructions to help you contribute to this snap.
0 kommentar(er)
