operator-framework / operator-framework/java-operator-sdk
Main (and v1) Branch Protection Rules and PR enforcement
Nobody has claimed this yet.
- Dominant language
- Java
- Stars
- 944
- Forks
- 242
- Avg merge
- 1d 4h
- Merged PRs (30d)
- 43
Description
Currently the main branch is not protected, so users with write access can directly push to main and v1. We could enforce to have PRs always (what we anyway do now), but the release action would not be able to do pom.xml version updates directly neither. This is one issue to solve / discuss.
The other part to discuss below this issue is it would be an idea to force approvals from code owners, since this is relatively small team it would not be convenient (think holidays), but with 1 required code owner approval for all PRs could work.
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
Review the branch protection settings for main and v1, then inspect the release action and its pom.xml version update. First clarify whether direct release updates must remain possible and whether code-owner approval is required; done means an agreed protection policy that still allows releases to work.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, github-actions, java
- Domain
- ci-cd, devops, release
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 25/100