theupdateframework / theupdateframework/taps
master branch protection
Open
Nobody has claimed this yet.
question
- Dominant language
- No language data
- Stars
- 37
- Forks
- 23
- PR merge metrics
- No merged PRs in 30d
Description
For the master branch, could we:
- require signed commits?
- require >=2 reviews?
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
Review the repository's master branch protection settings and determine how to apply the two requested requirements: signed commits and at least two reviews. Done means both requirements are enabled and verified; the issue names no files or tests, and its repository settings must be checked directly.
Written by the indexing model from the issue text.
Assessment
- Domain
- security
- Issue type
- Feature
- Difficulty
- 2/5
- Estimated time
- 1-3 hours
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100