-
-
Notifications
You must be signed in to change notification settings - Fork 14.7k
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: add mergify rules for nixpkgs #360340
Conversation
This comment was marked as spam.
This comment was marked as spam.
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.
Looks good to me, but I have no way to test this.
Question: Let's say an workflow only runs on certain paths, like #361447 (on |
Let's deploy it for now. We can always push a bugfix later, if we need any changes. |
I think we would actually mergify installed for this to work. Doesn't think this is the case just now: NixOS/org#39 |
Mergify is now active on the repo |
Thanks. Looks like merge queues need to be enabled separately. |
@Mic92 Enabled now |
I just had @Lassulus disable this as it was opening a Pull request per minute https://github.com/NixOS/nixpkgs/pulls?q=is%3Apr+is%3Aclosed+author%3Amergify%5Bbot%5D |
Things done
Context: NixOS/org#38
We already deployed mergify in nixos-hardware: NixOS/nixos-hardware#1249 and in nix https://github.com/NixOS/nix/blob/master/.mergify.yml
This pull requests adds support for it in nixpkgs. Mergify adds support for declarative merge queues to nixpkgs. Merge queues make sure that pull request are tested against the latest base branch. The advantage over github's own merge queues is that, the configuration is part of the repository and therefore does not require a repository admin to keep "Required Checks" in sync with recently added CI checks.
Another advantage mergify has it's that it is a github app. There are many cases where github won't run checks on automated created pull requests. With mergify this is not an issue. If we are happy with the workflow introduced mergify, we can proceed adding it to
CONTRIBUTING.md
.We have a similar feature in merge-bot. However it doesn't work very reliable. With mergify, we can later make
merge-bot
just add a label remove the complicated code and database integration we have just now.nix.conf
? (See Nix manual)sandbox = relaxed
sandbox = true
nix-shell -p nixpkgs-review --run "nixpkgs-review rev HEAD"
. Note: all changes have to be committed, also see nixpkgs-review usage./result/bin/
)Add a 👍 reaction to pull requests you find important.