Allow publishing when tagged commits are promoted #41
Conversation
This file contains 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
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.
PR Description
Currently, this plugin throws an error whenever it gets executed as part of a pipeline outside the tag event.
Motivation
In my use case, I find it useful to produce a test build of my android app when a commit is tagged. After the build is tested, I would like to promote the tagged commit so that a production version of the app is built and signed.
This plugin does not allow the production build to be published to Gitea releases simply because the event that executed the pipeline is not a tag event, even though the commit is tagged just fine.
This PR is meant to address this issue