Skip to content
Closed
Changes from all commits
Commits
File filter

Filter by extension

Filter by extension


Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
10 changes: 10 additions & 0 deletions .github/workflows/eval.yml
Original file line number Diff line number Diff line change
Expand Up @@ -267,3 +267,13 @@ jobs:
GH_TOKEN: ${{ github.token }}
REPOSITORY: ${{ github.repository }}
NUMBER: ${{ github.event.number }}

- name: Adding comments
Copy link
Member

@Mic92 Mic92 Dec 2, 2024

Choose a reason for hiding this comment

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

I am not so sure about comments here. This will be posted everytime someone pushes to a pull request and a new eval starts. This sounds noisy to me and makes long-running pull requests reviews hard to read. We mostly care for these changes if they are mass rebuilds and for that we have labels.

Copy link
Contributor Author

@azuwis azuwis Dec 2, 2024

Choose a reason for hiding this comment

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

How about gh pr comment "$NUMBER" --edit-last --body-file comparison/step-summary.md?

It should post only 1 comment, and update it on every push.

if: ${{ github.event_name == 'pull_request_target' }}
run: |
# Add the step summary as a comment
gh pr comment "$NUMBER" --body-file comparison/step-summary.md
env:
GH_TOKEN: ${{ github.token }}
GH_REPO: ${{ github.repository }}
NUMBER: ${{ github.event.number }}