ci: use "push.tags" webhook event #371
Closed
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
For more information, see anton-yurchenko/git-release#100
PaulRBerg
force-pushed
the
ci/webhook-event
branch
from
a29ede0
to
24815ec
Compare
|
Is the |
|
No, it is not fired when you create a GitHub release via the GitHub UI. https://docs.github.com/en/webhooks-and-events/webhooks/webhook-events-and-payloads#push In this case, I think it would be best to keep it as is, but FYI the workflow will stop working once Forge Std moves to an automated way of generating the releases themselves. |
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.
Makes the workflow added in #366 more robust by using the
pushwebhook event instead ofrelease, which doesn't work with releases made by other GitHub Actions workflows.For more information, see anton-yurchenko/git-release#100.