✨ Refactor and add support for triggering with workflow dispatch events #32
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.
✨ Refactor and add support for triggering with workflow dispatch events.
For this action to work, the workflow has to be on the repo before the PR that is being merged was created, so that the commit merging the PR already has the workflow, even though it actually runs on the main branch.
The main thing I want from it is to help me save time adding "latest changes" for already existing PRs.
Another option would be to rebase before merging, but that's not always possible.
This update should allow enabling a
workflow dispatch, to trigger the action manually with a PR number right after merging. In those cases, it won't be as great as everything happening automatically (as for PRs created after the workflow is added), but it will still save some steps and human errors by only needing the PR number.And it seems there's no way around it with the current available GitHub Actions events.