killercup / killercup/cargo-edit
Make it easier to manage version metadata
Nobody has claimed this yet.
- Dominant language
- Rust
- Stars
- 3.5k
- Forks
- 166
- PR merge metrics
- No merged PRs in 30d
Description
Inspired by crate-ci/cargo-release#637, I suspect we could make the version metadata easier to manage. As cargo set-version doesn't have a config file, we'd likely want to be opinionated since it doesn't help to have to set the value on the command line as well. I proposed having the "persistent" behavior described in the cargo-release issue.
Contributor guide
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 cargo set-version command and compare the persistent behavior proposed in crate-ci/cargo-release#637. Determine how version metadata is currently supplied and where a project-level value could be managed. Done means agreeing on an opinionated persistent configuration behavior and documenting its expected use.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 30/100