Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

not sync code when exec cargo publish command #8935

Open
baoyachi opened this issue Dec 3, 2020 · 1 comment
Open

not sync code when exec cargo publish command #8935

baoyachi opened this issue Dec 3, 2020 · 1 comment
Labels
A-git Area: anything dealing with git C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-publish S-propose-close Status: A team member has nominated this for closing, pending further input from the team S-triage Status: This issue is waiting on initial triage.

Comments

@baoyachi
Copy link

baoyachi commented Dec 3, 2020

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.

@baoyachi baoyachi added the C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` label Dec 3, 2020
@ehuss ehuss added A-git Area: anything dealing with git Command-publish labels Dec 4, 2020
@epage epage added the S-triage Status: This issue is waiting on initial triage. label Nov 20, 2024
@epage
Copy link
Contributor

epage commented Dec 20, 2024

I propose we close this for similar reasons as #841. This is about a wider release process that we don't have knowledge of nor do I feel like we are ready to be opinionated about. We don't know what branches you are allowed to release from, what branches are the proper remotes, and the push may happen after the publish, especially if you only want to tag on a successful release.

@epage epage added the S-propose-close Status: A team member has nominated this for closing, pending further input from the team label Dec 20, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
A-git Area: anything dealing with git C-feature-request Category: proposal for a feature. Before PR, ping rust-lang/cargo if this is not `Feature accepted` Command-publish S-propose-close Status: A team member has nominated this for closing, pending further input from the team S-triage Status: This issue is waiting on initial triage.
Projects
None yet
Development

No branches or pull requests

3 participants