Skip to content

workflows/eval: Add the step summary as a comment#360962

Closed
azuwis wants to merge 1 commit intoNixOS:masterfrom
azuwis:push-tkrysvvvymvq
Closed

workflows/eval: Add the step summary as a comment#360962
azuwis wants to merge 1 commit intoNixOS:masterfrom
azuwis:push-tkrysvvvymvq

Conversation

@azuwis
Copy link
Contributor

@azuwis azuwis commented Dec 2, 2024

See it in action azuwis#7

Make #360339 more discoverable.

Things done

  • Built on platform(s)
    • x86_64-linux
    • aarch64-linux
    • x86_64-darwin
    • aarch64-darwin
  • For non-Linux: Is sandboxing enabled in nix.conf? (See Nix manual)
    • sandbox = relaxed
    • sandbox = true
  • Tested, as applicable:
  • Tested compilation of all packages that depend on this change using nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD". Note: all changes have to be committed, also see nixpkgs-review usage
  • Tested basic functionality of all binary files (usually in ./result/bin/)
  • 25.05 Release Notes (or backporting 24.11 and 25.05 Release notes)
    • (Package updates) Added a release notes entry if the change is major or breaking
    • (Module updates) Added a release notes entry if the change is significant
    • (Module addition) Added a release notes entry if adding a new NixOS module
  • Fits CONTRIBUTING.md.

Add a 👍 reaction to pull requests you find important.

@github-actions github-actions bot added 6.topic: policy discussion Discuss policies to work in and around Nixpkgs 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions labels Dec 2, 2024
@github-actions github-actions bot added 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux. labels Dec 2, 2024
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.

@FliegendeWurst
Copy link
Member

I am not in favor of this change. It will make the GH search results even more useless, since searching for a package would then also find all dependency updates.

@Mic92
Copy link
Member

Mic92 commented Dec 2, 2024

That's also a good point. Less close it.

@Mic92 Mic92 closed this Dec 2, 2024
@azuwis azuwis deleted the push-tkrysvvvymvq branch December 2, 2024 08:31
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions 6.topic: policy discussion Discuss policies to work in and around Nixpkgs 10.rebuild-darwin: 0 This PR does not cause any packages to rebuild on Darwin. 10.rebuild-linux: 0 This PR does not cause any packages to rebuild on Linux.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants