feat: emit error annotations in GitHub Actions #2568
Merged
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
When a task fails in GitHub Actions, finding the error often means scrolling through hundreds of lines of logs. This PR changes that.
Task now automatically emits
::error::annotations when running in GitHub Actions (GITHUB_ACTIONS=true). These annotations:Before
Errors are buried in logs, easy to miss when you have dozens of tasks running.
After
::error title=Task 'build' failed::exit status 1
The error appears as a red annotation at the top of the workflow run, visible at a glance.
Why this matters
Test plan
GITHUB_ACTIONS=true task failing-taskemits::error title=Task 'X' failed::...GITHUB_ACTIONS=true, no annotation is emitted