mheap / mheap/github-default-branch
Copy branch protections rather than renaming the pattern
Nobody has claimed this yet.
- Dominant language
- JavaScript
- Stars
- 134
- Forks
- 9
- PR merge metrics
- No merged PRs in 30d
Description
https://github.com/mheap/github-default-branch/issues/4#issuecomment-646299374
I think you have the feature to keep the previous branch around. So maybe it should not be an update of the pattern, but a copy of the settings?
If we skip deleting the old branch (using --skip-delete-old-branch), we should copy the settings instead of updating the protection to point at our new branch
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.
Research direction
Start by locating the JavaScript CLI handling for --skip-delete-old-branch and the code that updates branch protection when the default branch changes. Check how the existing branch protection settings are accessed, then verify that retaining the old branch leaves its settings copied to the new branch rather than moving them.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github, javascript
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 45/100