Support deployment events #2629
Open
Conversation
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
2 tasks
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
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.
Fixes: #2631
I added support for deployment events (see deployment webhooks) and tested this in one of my work's repos.
I had to add another fetch for the default branch in
getSHAForNonPullRequestEventbecause otherwise I saw the following error:This might be because
env.GITHUB_REF_NAMEwasn't set when the Action was triggered by a deployment event. It is set properly when this Action is triggered by amerge_groupevent. (I'm not sure on this, I was having a hard time figuring out where the Action does the fetch for merge_group events).