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

error: unable to commit to git with <BUMP> = skip #174

Open
onkoe opened this issue Oct 20, 2024 · 2 comments
Open

error: unable to commit to git with <BUMP> = skip #174

onkoe opened this issue Oct 20, 2024 · 2 comments

Comments

@onkoe
Copy link

onkoe commented Oct 20, 2024

Noticed something weird with my crate, pisserror, when trying to publish a new version with cargo workspaces.

Everything is up-to-date, and all commits are pushed to origin.

Looks like a reappearance of #60 ..?

barrett@farts ~/D/p/pisserror (main) [2]> cargo workspaces publish
info looking for changes since [email protected]
info current common version 0.3.0-rc.1
✔ Select a new version (currently 0.3.0-rc.1) · Skip (stays 0.3.0-rc.1)

Changes:

✔ Are you sure you want to create these versions? · yes
     Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 3 unchanged dependencies behind latest
info version committing changes
error: unable to commit to git, out = On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean, err = 
barrett@farts ~/D/p/pisserror (main) [1]> cargo workspaces publish -- -verbose
error: "-verbose" isn't a valid value for '<BUMP>'
	[possible values: major, minor, patch, premajor, preminor, prepatch, skip, prerelease, custom]

USAGE:
    cargo workspaces publish <BUMP>

For more information try --help
barrett@farts ~/D/p/pisserror (main) [2]> cargo workspaces publish skip -- --verbose
error: Invalid value "--verbose" for '<CUSTOM>': encountered unexpected token: Hyphen

For more information try --help
barrett@farts ~/D/p/pisserror (main) [2]> cargo workspaces publish skip --verbose
error: Found argument '--verbose' which wasn't expected, or isn't valid in this context

	If you tried to supply `--verbose` as a value rather than a flag, use `-- --verbose`

USAGE:
    cargo workspaces publish <BUMP>

For more information try --help
barrett@farts ~/D/p/pisserror (main) [2]> cargo workspaces publish skip
info looking for changes since [email protected]
info current common version 0.3.0-rc.1

Changes:

✔ Are you sure you want to create these versions? · yes
     Locking 0 packages to latest compatible versions
note: pass `--verbose` to see 3 unchanged dependencies behind latest
info version committing changes
error: unable to commit to git, out = On branch main
Your branch is up to date with 'origin/main'.

nothing to commit, working tree clean, err = 
@martin-g
Copy link

'barrett@farts ~/D/p/pisserror (main) [1]> cargo workspaces publish -- -verbose'

Here you pass a single '-' before verbose.

@onkoe
Copy link
Author

onkoe commented Oct 20, 2024

Yes, but unfortunately, the ones without that mistake are also broken!

Just wanted to show all the stuff I tried, as the error messages were a little confusing. 😅

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

2 participants