feat: enhance post-annotations to support both workflow_run and same-workflow scenarios #285
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.
Summary
This PR enhances the
post-annotations
functionality to work in both workflow_run scenarios (fork PRs) and same-workflow scenarios (regular PRs with split jobs).Changes
actions/download-artifact@v4
for same-workflow scenariosgithub.event.workflow_run.id
andgithub.run_id
Use Cases
This enhancement supports three scenarios:
Fork PRs (existing functionality preserved):
workflow_run
downloads and posts themRegular PRs with split jobs (new functionality):
save-annotations: true
post-annotations: true
to download and post annotations from same workflowRegular PRs (existing direct posting still works):
Testing
The changes maintain backward compatibility while adding new capabilities. The fallback mechanism ensures that if one approach fails, the other is attempted.
Related Issues
Addresses the limitation where
post-annotations
only worked with workflow_run events, now enabling its use in regular branch PRs with split-job configurations.