workflows/check: run "checks" in one workflow

[wolfgangwalther]

This introduces "check" as another category of jobs suitable for the "Require status checks to pass" feature.

Checks as a category would include everything that is done before even looking at the code: Right branch? Commit messages? Cherry-picked correctly?

(commit messages are not checked, yet)

Split off from #415006 to make review and merge in steps possible. See that PR for rationale.

Things done

• Tested in my fork via workflows/{pr,push}: init #415006.
• Fits CONTRIBUTING.md, pkgs/README.md, maintainers/README.md and other contributing documentation in corresponding paths.

---

Add a 👍 reaction to pull requests you find important.

[nixpkgs-ci]

Backport failed for release-24.11, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-24.11
git worktree add -d .worktree/backport-416369-to-release-24.11 origin/release-24.11
cd .worktree/backport-416369-to-release-24.11
git switch --create backport-416369-to-release-24.11
git cherry-pick -x f11b58a7a099b701c3d929ea2cded036a0a5dafd

[nixpkgs-ci]

Backport failed for release-25.05, because it was unable to cherry-pick the commit(s).

Please cherry-pick the changes locally and resolve any conflicts.

git fetch origin release-25.05
git worktree add -d .worktree/backport-416369-to-release-25.05 origin/release-25.05
cd .worktree/backport-416369-to-release-25.05
git switch --create backport-416369-to-release-25.05
git cherry-pick -x f11b58a7a099b701c3d929ea2cded036a0a5dafd

[nixpkgs-ci]

Successfully created backport PR for release-24.11:

• [Backport release-24.11] workflows/check: run "checks" in one workflow #416402

[nixpkgs-ci]

Successfully created backport PR for release-25.05:

• [Backport release-25.05] workflows/check: run "checks" in one workflow #416406

[vcunat]

FYI, the check seems to misunderstand the staging-next-25.05 workflow. It complains about perfectly clean merges that merged correct (even automatic) cherry-picks into staging-25.05. It even complains about

Merge remote-tracking branch 'origin/master' into staging-next-25.05

See basically any complaint in #418358 (review)

[wolfgangwalther]

Thanks for the report, will look into this. I'd say it doesn't make sense to run the check cherry-picks workflow on the staging PRs at all.