Skip to content

Conversation

@deniak
Copy link
Member

@deniak deniak commented Oct 3, 2025

When an error occurs, people are required to dig into the logs to find what went wrong, e.g. https://github.com/w3c/aria/actions/runs/18193307801
Screenshot 2025-10-03 at 17 27 50

@daniel-montalvo suggested to use the annotations to surface the errors so we don't have to check logs.
That PR makes use of the actions toolkit to add the annotations when there's an error.

@deniak deniak requested a review from sidvishnoi October 3, 2025 13:29
console.log(message);
} else {
console.log(message);
console.error(message);
Copy link
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I guess we can remove the console.error?

Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

I couldn't find if core.error would still display the error in the logs themselves so I kept it.

@sidvishnoi sidvishnoi changed the title surface errors in the annotations fix: surface exit errors in the annotations Oct 6, 2025
@daniel-montalvo
Copy link
Contributor

Thanks @deniak and @sidvishnoi for looking into this. This is going to be a great time saver!

@sidvishnoi
Copy link
Member

Hi, I'll merge and release this once I figure out #213. Without it, I'll have to revert some commits to get this PR in. I hope it's ok to have status quo for a few more days.

@deniak
Copy link
Member Author

deniak commented Oct 6, 2025

Thanks @sidvishnoi. No rush, please deploy at your convenience.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

4 participants