WIP: Harmonize branch protection rules
Open
@mberz is already working on this.
Since Feb 6, 2026.
maintenance
- Dominant language
- Python
- Stars
- 3
- Forks
- 2
- Avg merge
- 2d 3h
- Merged PRs (30d)
- 3
Description
Repository rules
We would like harmonize repository rules across repositories.
First step is to agree on a set of rules:
https://github.com/organizations/pyfar/settings/rules
Strongly suggested based on current rules (see below)
- Restrict deletions
- Require a PR before merging
- require 2 reviews
- Require workflows to pass before merge
- Require up to date with base branch
- Block force pushes
Additionally suggested
- Require linear history
- Require approval most recent push
Additional considerations
- Define rules to specify which repos and branches are to be affected.
Branch protection rules
pyfar
- Require PR to merge
- require 2 reviews
- Require status checks to pass
- Allow force pushes by everyone
spharpy
- Require PR to merge
- require 1 review
- Require status checks to pass
- require branches to be up to date
- Allow force pushes by everyone
pyrato
- Require PR to merge
- require 2 reviews
- Allow force pushes by everyone
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.
Assessment
This issue has not been assessed yet.