Modify check-pr to support issue assignment requirement
Nobody has claimed this yet.
- Dominant language
- Nushell
- Stars
- 5.1k
- Forks
- 91
- PR merge metrics
- No merged PRs in 30d
Description
Hey 👋
Thanks for this initiative! 💪
Would be nice to also configure auto-close of pull requests from non-collaborators that either have no bound GitHub issue/s or the issues are not assigned to the pull request submitter's account.
I want to first review an issue, greenlight and assign it manually to a specific vouched account.
I want to avoid 2 or more vouched accounts submitting competing pull requests for the same issue. I want visibility on who is working on what. I want to delay work on certain parts of the system to avoid conflicts when necessary.
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 by locating the check-pr entry point and reading how pull requests from non-collaborators are currently evaluated. Define the behavior for pull requests with no linked issue or with an issue not assigned to the submitter, then verify that those cases are automatically closed while assigned, approved work remains eligible.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, shell
- Domain
- ci-cd, tooling
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100