[security] Enforce Branch Protections
Open
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 323
- Forks
- 133
- Avg merge
- 2d 8h
- Merged PRs (30d)
- 2
Description
This is an issue generated by (for-internal-use-only)github-tools
Description
This repository has exceeded the development grace period, and the repo owner must decide if branch protections should be enforced.
If this repository houses code used in production in any capacity, branch protections must be enforced. Read (for-internal-use-only)here for more details
What do I need to do?
- You can control whether or not branch protections are enforced by exclusively creating either of the labels:
'enforce-branch-protections: true' or 'enforce-branch-protections: false' - If there is no branch protection control label, this issue will be recreated.
- Once you have created either label, you can close this issue.
- If you have issues or questions, please reach out to #internal-security-n-compliance on slack.
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
Follow the issue instructions and decide whether this production repository requires branch protections. Apply exactly one of the enforce-branch-protections: true or enforce-branch-protections: false labels; completion is the label being present and the issue being closed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github
- Domain
- security
- Issue type
- Feature
- Difficulty
- 1/5
- Estimated time
- Under an hour
- Activity status
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 25/100