Change PR requirements on merge to master (1 review, core or maintainer)
Open
Nobody has claimed this yet.
enhancement
- Dominant language
- Python
- Stars
- 322
- Forks
- 255
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 5
Description
From nf-core 2025 Core + Steering Retreat.
Proposed change: Require 1 review from core team or maintainer before merging to master branch.
Note: Review should focus on guidelines compliance only.
Context: Streamline PR review process while maintaining quality standards.
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 repository's branch protection and pull request merge settings for the master branch. Confirm how the existing rules handle reviews and team membership, then verify that one review from a core team member or maintainer is required and that the rule is limited to guidelines compliance.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- ci-cd
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100