Strengthen branch protections
Nobody has claimed this yet.
- Dominant language
- Julia
- Stars
- 70
- Forks
- 20
- Avg merge
- 5h 17m
- Merged PRs (30d)
- 7
Description
I accidentally pushed to main directly for https://github.com/SciML/ADTypes.jl/commit/b7ba2870bde294c6834b6541a657901062a6aec2 and the repo didn't stop me. Perhaps we should add rules so that such pushes are impossible, even for people with the necessary permissions? There is one to require pull requests but we may need to tick the box that says it applies to all roles.
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
Open the repository settings and review the branch protection rule that requires pull requests. Check whether the setting can apply to all roles, then verify that direct pushes to main are rejected, including for users with the necessary permissions.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- devops, security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100