Make main and stable branches protected branches
Open
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 6
- Forks
- 1
- Avg merge
- 1d 3h
- Merged PRs (30d)
- 10
Description
Hello,
I committed directly to stable34 by accident.
See https://github.com/nextcloud/office/commit/49656aa418d045179de231819896e61e6f9eb97f
Branch "main" is also unprotected.
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 in the GitHub repository settings and inspect the branch protection configuration for main and stable branches; the issue also references stable34 and commit 49656aa418d045179de231819896e61e6f9eb97f. Done means main and stable are protected so accidental direct commits are prevented.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Quiet
- Clarity
- Clearly specified
- Newbie friendliness
- 48/100