-
Notifications
You must be signed in to change notification settings - Fork 127
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
ci: Delete QNS PR comment on successful run #1807
Conversation
Because we only add one when there is a failure, and when things then later get fixed we don't update it again (because we skip the update on success). So the outdated, failed state keeps being shown.
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.
Unfortunate to have it show up on each successful pull request then, i.e. more noise. That said, maybe better than the above mentioned confusion.
Do you see a way to only update an existing comment, rather than always add or updated? |
On success, we could use https://github.com/thollander/actions-comment-pull-request?tab=readme-ov-file#action-inputs |
Oh nice! |
Co-authored-by: Max Inden <[email protected]> Signed-off-by: Lars Eggert <[email protected]>
…to ci-qns-always-comment
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.
Neat! Thank you!
Benchmark resultsPerformance differences relative to 7ff76c7.
Client/server transfer resultsTransfer of 134217728 bytes over loopback.
|
Because we only add one when there is a failure, and when things then later get fixed we don't update it again (because we skip the update on success). So the outdated, failed state keeps being shown.Because if we only update on failure, we keep showing the last-failed state after success.