fix: support workflow_run events for github status
#6
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
ensures commit statuses are posted to the correct sha when the action is triggered from a workflow_run context (e.g., secure fork pr workflows) applies the same fix as ipshipyard/ipfs-deploy-action#37
2color
reviewed
Aug 25, 2025
2color
reviewed
Aug 25, 2025
Contributor
2color
left a comment
2color
left a comment
There was a problem hiding this comment.
Overall LGTM. See my comments.
Co-authored-by: Daniel Norman <1992255+2color@users.noreply.github.com>
- update dual workflows section title for clarity - prepare for v1.0.0 release
v1.0.0Added
Fixed
|
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.
ensures commit statuses are posted to the correct sha when the action is triggered from a
workflow_runcontext (e.g., in fork pr workflows)unlikely people will need this (usually this only runs on main branches), but for consistency we want to support the same behavior as in ipshipyard/ipfs-deploy-action#37