Don't label PRs with moved expressions with `has: package(new)`
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 323
- Forks
- 171
- PR merge metrics
- No merged PRs in 30d
Description
Have a look at the following PR for instance: https://github.com/NixOS/nixpkgs/pull/36934
This PR did a minor rename change, however the PR was labeled to contain a new package which might be a bit misleading especially when the PR aims to fix a package that might be relevant for the upcoming release.
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 examining the referenced nixpkgs pull request and tracing ofborg's pull-request labeling behavior. Determine how moved expressions are identified and how the has: package(new) label is assigned; done means rename-only changes no longer receive that label while genuinely new packages still do.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- tooling
- Issue type
- Bug
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100