Create a workflow for publishing a release
Open
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 67
- Forks
- 13
- Avg merge
- 7h 37m
- Merged PRs (30d)
- 2
Description
Would be nice to have it automated and not just do it off of devboxes.
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
No files, tests, or entry points are named. Start by reviewing how this Rust crate is currently released from developer machines and identify the repository's release process. Done means releases are published through a repeatable automated workflow without relying on devboxes.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- ci-cd, release
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100