not sync code when exec cargo publish command
Open
Nobody has claimed this yet.
A-git
C-feature-request
Command-publish
S-propose-close
- Dominant language
- Rust
- Stars
- 15.5k
- Forks
- 3k
- Avg merge
- 23h 30m
- Merged PRs (30d)
- 51
Description
Sometimes we modify the code and execute git commit.
Then when we executed cargo publish, we found that the code had been published on crates.io, and the code had forgotten to submit to the corresponding branch. Make the code and crates.io version not synchronized in time.
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
The issue names no files or tests; begin by reproducing the described workflow of modifying code, committing with git, and running cargo publish. Establish the expected relationship between the published crates.io contents and the corresponding branch, then verify that publishing cannot leave them out of sync.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- rust
- Domain
- release, tooling
- Issue type
- Bug
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 32/100