nixpkgs: Give maintainers the ability to link issues and PRs
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 48
- Forks
- 36
- Avg merge
- 2m
- Merged PRs (30d)
- 3
Description
Currently committers have the ability to link issues and PRs, such that when the PR is merged, the issue is automatically closed. However, despite having the ability to manually close issues, regular maintainers cannot do this unless they control the original PR and use a closing keyword in the description.
This increases the burden of work for maintainers who triage incoming issues and link existing issues to PRs, as the issue requires either committer action or a manual follow-up to be closed. It also creates more noise, can't be filtered for, and is less clear at a glance.
If possible with enterprise permission controls, please grant maintainers this permission. (I couldn't figure out from what I can see publically whether this can be individually configured.) If not, this may be a good thing to bring up with GitHub as a low-priority item.
Contributor guide
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 with GitHub's linked issue and pull request permission documentation, then inspect the organization-level controls available to maintainers. Verify whether this permission can be granted independently; if it cannot, record the limitation and the proposed GitHub follow-up as the completed outcome.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- developer-experience
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Quiet
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100