Skip to content

Conversation

@Mic92
Copy link
Member

@Mic92 Mic92 commented May 24, 2025

based on #1142

@Mic92 Mic92 requested a review from a team as a code owner May 24, 2025 08:14
@Mic92 Mic92 changed the title Automatically nix manual Automatically update nix manual May 24, 2025
@Mic92 Mic92 force-pushed the ci-cd branch 4 times, most recently from b5703bf to 95f73ea Compare May 24, 2025 08:26
@Mic92
Copy link
Member Author

Mic92 commented May 24, 2025

@Mic92 Mic92 enabled auto-merge (rebase) May 27, 2025 14:18
@Mic92 Mic92 merged commit 94ef8ad into NixOS:master May 27, 2025
4 checks passed
@Mic92 Mic92 deleted the ci-cd branch May 27, 2025 14:20
@fricklerhandwerk
Copy link
Collaborator

Thanks! I don't see why we should run an update every day though, seems very wasteful. Before the automation I ran the command manually around each release and it was fine. We may as well do a workflow_dispatch and add a line to the Nix release instructions to hit that button on GitHub. Once we migrate Nixpkgs/NixOS manuals here, we can do the same for stable and only bump unstable every 24h.

@Mic92
Copy link
Member Author

Mic92 commented May 27, 2025

Do you think so? It may just run a minute or so. Probably peanuts compared to what we do in nixpkgs. I got complaints about the missing manual in less then 24h. The idea was that we never have to run this again manually. I wasn't even aware of this process until someone told me the manual is out of date.

@fricklerhandwerk
Copy link
Collaborator

fricklerhandwerk commented May 28, 2025

Just because we're likely burning embarrassing amounts of ancient phytoplankton with Nixpkgs doesn't mean that it's alright or that we have to do any more of that... We probably can't simply make it pull-based, but should be easy enough to add gh repo clone nixos/nix.dev && cd nix.dev && gh workflow run ... to the release script (or at least the manual steps), no?

@Mic92
Copy link
Member Author

Mic92 commented May 28, 2025

If you want to stay on top of these things? For the last release it was delayed. Personally I find my time more valuable than some github action that runs every now and than.

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