paritytech / paritytech/json-rpc-interface-spec
Add `main` as a protected branch
Open
Nobody has claimed this yet.
- Dominant language
- No language data
- Stars
- 37
- Forks
- 6
- PR merge metrics
- No merged PRs in 30d
Description
Right now it's convenient to push to main, but once this repository is made public and becomes normative, the main branch should be protected so that people don't push to it.
Two approvals should be needed to merge PRs.
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 in the repository's branch protection settings for main. Configure main to require two approvals before merging and prevent direct pushes, then verify that the protection rules are active.
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
- Stale
- Clarity
- Clearly specified
- Newbie friendliness
- 35/100