Skip to content

[Backport release-25.05] ci/request-reviews: untangle owner-related bash code#457831

Merged
wolfgangwalther merged 4 commits intorelease-25.05from
backport-457503-to-release-25.05
Nov 2, 2025
Merged

[Backport release-25.05] ci/request-reviews: untangle owner-related bash code#457831
wolfgangwalther merged 4 commits intorelease-25.05from
backport-457503-to-release-25.05

Conversation

@nixpkgs-ci
Copy link
Copy Markdown
Contributor

@nixpkgs-ci nixpkgs-ci bot commented Nov 2, 2025

Bot-based backport to release-25.05, triggered by a label in #457503.

  • Before merging, ensure that this backport is acceptable for the release.
    • Even as a non-committer, if you find that it is not acceptable, leave a comment.

Instead of requesting owners and maintainer separately, each with their
own limit of 10 review requests, we now run this together. This unties
the logic and allows easier refactoring. Also, it gives us a consistent
threshold of when not to request reviews anymore, which I set to 15.
Before, this could have been anything between 10 and 20, depending on
how the reviewers distributed over owners and maintainers.

(cherry picked from commit b2d1946)
This is just a refactor, no functional change. It is a preparation for a
future change, where `get-code-owners.sh` can be moved entirely into
eval/compare. This can only happen once we removed the remaining `gh
api` calls from it.

(cherry picked from commit d177d60)
All the github related logic is now bundled in `request-reviewers.sh`.
This allows moving the `get-code-owners.sh` file into the eval/compare
step in the next commit.

(cherry picked from commit 18ab6b7)
This moves the parsing of ci/OWNERS into the Nix sandbox. We also get
rid of checking out the nixpkgs repo another time in the reviewers
workflow - we already have everything we need in the eval/compare job.

The creation of owners.txt in this way is only temporary, it should
eventually be moved further, similar to how maintainers.json is
currently migrating to a maintainer map for the whole repo stored on the
target branch as artifact.

(cherry picked from commit 3bef0dc)
@wolfgangwalther wolfgangwalther added this pull request to the merge queue Nov 2, 2025
@nixpkgs-ci nixpkgs-ci 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 Nov 2, 2025
@nix-owners nix-owners bot requested review from Mic92 and philiptaron November 2, 2025 15:48
@nixpkgs-ci nixpkgs-ci bot added 6.topic: continuous integration Affects continuous integration (CI) in Nixpkgs, including Ofborg and GitHub Actions 4.workflow: backport This targets a stable branch labels Nov 2, 2025
@nix-owners nix-owners bot requested review from MattSturgeon and zowoq November 2, 2025 15:48
@nixpkgs-ci nixpkgs-ci bot added the 6.topic: policy discussion Discuss policies to work in and around Nixpkgs label Nov 2, 2025
@nix-owners nix-owners bot requested a review from wolfgangwalther November 2, 2025 15:48
Merged via the queue into release-25.05 with commit f4498a8 Nov 2, 2025
49 of 50 checks passed
@wolfgangwalther wolfgangwalther deleted the backport-457503-to-release-25.05 branch November 2, 2025 15:51
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

4.workflow: backport This targets a stable branch 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.

1 participant