Conversation
Contributor
|
Looks cool, I'm not familiar enough with github actions can these be limited to release only (ie. there is no reason to run a build on every push/merge) |
Contributor
Author
|
How about setting the release trigger? Are you using the release mechanism already? |
Contributor
Author
|
https://github.com/thigg/gpodder-sailfish/releases/tag/vtestrelease3 The current config is creating a release if you push a tag that starts with v |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Proof-of-Concept github builds the rpm automatically.
Can be seen on my master branch: https://github.com/thigg/gpodder-sailfish/actions
Sources: https://github.com/CODeRUS/screencast/blob/master/.github/workflows/build.yml, https://forum.sailfishos.org/t/build-sailfish-os-application-using-github-actions-or-gitlab-ci/2147