Skip to content
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

Tracking: repeatable treewides #346453

Open
pbsds opened this issue Oct 4, 2024 · 8 comments
Open

Tracking: repeatable treewides #346453

pbsds opened this issue Oct 4, 2024 · 8 comments
Labels
5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems

Comments

@pbsds
Copy link
Member

pbsds commented Oct 4, 2024

This is a overview/tracking issue for various easy-to-grep and possibly scriptable janitor treewides, that address mostly benign issues that are prone to slip through review and pile up. Please do link other treewides that fit the bill.

Please don't bog down this issue with by-name migrations, meta.mainProgram additions and with lib removal spam 👍 (unless their creation and testing is fully scripted, enabling full tree coverage and near zero toil)

Other chores:

Feel free to ping me for review :)

@pbsds pbsds added the 5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems label Oct 4, 2024
@philiptaron
Copy link
Contributor

Thank you for this list, and the clear and kind guidelines that accompany it Peder (@pbsds)!

In the absolute fullness of time, I hope that each of these ends up being in nixpkgs-vet with an autofix mode.

CC @infinisil @willbush.

@pbsds
Copy link
Member Author

pbsds commented Oct 4, 2024

I assume this is more in scope for https://github.com/nix-community/nixpkgs-lint?

@patka-123
Copy link
Contributor

This one might be interesting to add to this list?
#347678

@pbsds
Copy link
Member Author

pbsds commented Jan 18, 2025

Notes to self

  • CI doesn't enumerate number of eval failures introduced by a PR, this either has to be done manually or added to CI
  • Use/adapt infinisil/treewide-nixpkgs-reformat-script for other treewides such that they don't interfere with currently open and active PRs

@philiptaron
Copy link
Contributor

#363585 needs to be repeated on some schedule (c.f. #373945)

@pbsds
Copy link
Member Author

pbsds commented Jan 28, 2025

#363585 needs to be repeated on some schedule (c.f. #373945)

This strikes me more as a dep-bump chore than treewide janitor work.

Interestingly in this particular case it is not really needed on a regular schedule but rather it should preferably only be triggered whenever for example nixfmt or nixpkgs-review are bumped. Should we create a separate chore-tracking issue, or is this rather a job for automatic GHA actions like the periodic merges from master to staging-next?

@philiptaron
Copy link
Contributor

This strikes me more as a dep-bump chore than treewide janitor work.

It's funny you should say that. To those without the taste to tell the difference, janitorial work is indeed a chore, and the word "repeatable" just emphasizes that. 🙂

I'm happy to follow your lead in whatever organizational scheme makes sense to you, including minimizing these comments and going about other sorts of work in this specific issue.

If action is to be taken, bumping this dependency on (say) a weekly schedule through a GitHub action which opened a PR would make sense to me. We do something like that in nixpkgs-vet:

But I currently don't have the stomach for working through the GitHub actions universe to do this for Nixpkgs, so it's just a finger pointing to the horizon at the moment.

@pbsds
Copy link
Member Author

pbsds commented Jan 28, 2025

In the meanwhile lets track such here

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
5. scope: tracking Long-lived issue tracking long-term fixes or multiple sub-problems
Projects
None yet
Development

No branches or pull requests

3 participants