opensearch-project / opensearch-project/.github
[PROPOSAL] Standardize and enforce branch protection
Open
@CEHENKLE is already working on this.
Since Jan 5, 2022.
campaign
- Dominant language
- No language data
- Stars
- 41
- Forks
- 74
- Avg merge
- 3d 19h
- Merged PRs (30d)
- 1
Description
What kind of business use case are you trying to solve? What are your requirements?
Branch protection is used to avoid accidentally deleting branches, requiring multiple code reviewers, etc.
What is the problem? What is preventing you from meeting the requirements?
Branch protection varies repo to repo, write up what kind of branch protection we want and standardize/enforce.
What are you proposing? What do you suggest we do to solve the problem or improve the existing situation?
Write up what branch protection rules each repository should apply, at a minimum.
What are remaining open questions?
- Should we allow for feature/x branches?
- We have bots, such as Whitesource and https://github.com/dblock/create-a-github-issue that open PRs and need to work around branch protection, how do they do that?
- https://github.com/opensearch-project/.github/issues/26
- Developers can push a branch accidentally, then they can't delete it, how do they do that?
- Do we cleanup stale branches and how? (Does it require temporarily relaxing branch protection?)
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.
Assessment
This issue has not been assessed yet.