Don't build when source is nixpkgs/staging or nixpkgs/staging-next
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Don't build when we merge staging-next or staging into, say. master. Checking evaluation is still a good thing, though.
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start by comparing the merge behavior described for staging and staging-next with the example in nixpkgs PR #45643. Trace the ofborg path that decides whether to build or only evaluate. Done means merges from those branches skip builds while evaluation still runs.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- build-system, ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100