We read every piece of feedback, and take your input very seriously.
To see all available qualifiers, see our documentation.
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
sublime-merge
A new version (2099) of sublime-merge was just pushed to the dev/candidate channel in the snap store. The following revisions are available.
dev/candidate
If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.
snap refresh sublime-merge --channel dev/candidate
snap version; lscpu | grep Architecture; snap info sublime-merge | grep installed
Maintainers can promote this to stable by commenting /promote <rev>[,<rev>] dev/stable [done].
/promote <rev>[,<rev>] dev/stable [done]
For example To promote a single revision, run /promote <rev> dev/stable To promote multiple revisions, run /promote <rev>,<rev> dev/stable To promote a revision and close the issue, run /promote <rev>,<rev> dev/stable done
For example
/promote <rev> dev/stable
/promote <rev>,<rev> dev/stable
/promote <rev>,<rev> dev/stable done
You can promote all revisions that were just built with:
/promote 89,90 dev/stable done
The text was updated successfully, but these errors were encountered:
The following screenshots were taken during automated testing:
Sorry, something went wrong.
data: screenshots for snapcrafters/sublime-merge#43
a2c4605
No branches or pull requests
A new version (2099) of
sublime-merge
was just pushed to thedev/candidate
channel in the snap store. The following revisions are available.Automated testing
If configured, the snap will be installed in a VM, and any test results or screenshots will be posted to this issue as a comment shortly.
How to test it manually
How to release it
Maintainers can promote this to stable by commenting
/promote <rev>[,<rev>] dev/stable [done]
.You can promote all revisions that were just built with:
The text was updated successfully, but these errors were encountered: