rigetti / rigetti/qcs-sdk-rust
Make the prerelease/release process more obvious
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 15
- Forks
- 4
- Avg merge
- 1h 9m
- Merged PRs (30d)
- 1
Description
This can be partly just documentation in the README, but we should potentially also adjust how the input to the prerelease workflow behave, and if possible, make it easier to see which jobs are triggered indirectly.
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 with the README and the prerelease workflow mentioned in the issue. Trace the workflow inputs and indirectly triggered jobs to determine which release steps need clearer documentation or behavior. Done means the prerelease/release process and triggered jobs are easier to understand, with any feasible input improvements addressed.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, documentation, release
- Issue type
- Documentation
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 35/100