-
Notifications
You must be signed in to change notification settings - Fork 640
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Enable annotations on failed tests #910
Conversation
@ssbarnea it works with |
.github/workflows/tox.yml
Outdated
@@ -179,6 +179,11 @@ jobs: | |||
with: | |||
name: logs.zip | |||
path: .tox/**/log/ | |||
- name: Report junit failures | |||
uses: shyim/junit-report-annotations-action@master |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I'm not sure about using master
. Should we wait till shyim/junit-report-annotations-action#3 (comment) gets addressed and pin it then?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is ok, the risk is very low. The token is read-only.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
My concern is not (only) about that:
- The action may suddenly break the interface.
- The token only has read-only mode for PR runs, there's still cron runs and tag creations that will run in-repo and have higher privileges.
Co-authored-by: Sviatoslav Sydorenko <wk.cvs.github@sydorenko.org.ua>
WIP: Currently waiting for shyim/junit-report-annotations-action#3 fixes.