rigetti / rigetti/rigetti-pyo3
Require PR with reviews to update `main`
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 11
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
The main branch currently doesn't require reviews, because prereleases weren't working with that protection applied.
We should figure out how to fix this.
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
Inspect the linked GitHub Actions run, especially job 72365694234, and the repository's current main-branch protection and prerelease workflow. Reproduce or identify why requiring reviews breaks prereleases; done means main requires reviewed PRs while prereleases still complete successfully.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- github-actions
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Quiet
- Clarity
- Needs clarification
- Newbie friendliness
- 38/100