Skip to content

Conversation

@Ma27
Copy link
Member

@Ma27 Ma27 commented Sep 21, 2025

@Ma27 Ma27 requested a review from a team as a code owner September 21, 2025 13:38
Copy link
Contributor

@wolfgangwalther wolfgangwalther left a comment

Choose a reason for hiding this comment

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

This branch should also be added to the no-force-push ruleset.

Also, I think you will need to add it to no-creation as well, otherwise... you can't create it in the first place.

@Ma27 Ma27 force-pushed the kernel-update-branch branch from 4c01341 to d436003 Compare September 21, 2025 13:58
Copy link
Contributor

@wolfgangwalther wolfgangwalther left a comment

Choose a reason for hiding this comment

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

I think this should work, yes.

@wolfgangwalther
Copy link
Contributor

I discussed the name a lot with @emilazy in NixOS/nixpkgs#437208. While I believe kernel-updates is better than staging-nixos, I also believe that both are way better than batch-with-kernel-updates. The former two follow already established patterns.

Thus, I agreed with @Ma27 on Matrix to go with staging-nixos.

I checked - and all branch protection rules already support this branch name accordingly. Thus I only temporarily disable the no-creation-except-release-team rule to allow myself to create the branch, then enabled it again.

The staging-nixos branch now exists, and I'm closing this as "completed".

Ma27 added a commit to Ma27/nixpkgs that referenced this pull request Oct 5, 2025
See NixOS#437208 (comment)
Depends on NixOS/org#172

As documented below, the idea is to essentially group all changes
rebuilding all VM tests with kernel updates and merge them together into
`master` whenever the Linux kernels get updated.

This documents the workflow of updates in the nixpkgs manual. While at
it, I removed the README from the packages because

* it's horribly outdated
* I didn't even know it exists which confirms that its discoverability
  was very poor

and added the relevant portions into the nixpkgs manual as well.
nixpkgs-ci bot pushed a commit to NixOS/nixpkgs that referenced this pull request Oct 6, 2025
See #437208 (comment)
Depends on NixOS/org#172

As documented below, the idea is to essentially group all changes
rebuilding all VM tests with kernel updates and merge them together into
`master` whenever the Linux kernels get updated.

This documents the workflow of updates in the nixpkgs manual. While at
it, I removed the README from the packages because

* it's horribly outdated
* I didn't even know it exists which confirms that its discoverability
  was very poor

and added the relevant portions into the nixpkgs manual as well.

(cherry picked from commit 9f95c2a)
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants