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

(Docs) Does --no-push also mean "no commit"? #770

Open
matthias-ccri opened this issue Sep 7, 2022 · 0 comments
Open

(Docs) Does --no-push also mean "no commit"? #770

matthias-ccri opened this issue Sep 7, 2022 · 0 comments
Labels
documentation Improvements or additions to documentation

Comments

@matthias-ccri
Copy link

matthias-ccri commented Sep 7, 2022

It seems like this is the case — specifying --no-push doesn't push, but it also doesn't commit changes either.

Should the docs be updated? (https://microsoft.github.io/beachball/cli/options.html#change-options)

From:

whether to push changes back to git remote origin

To

whether to commit and push changes back to git remote origin. --no-push does not commit.

@ecraig12345 ecraig12345 added the documentation Improvements or additions to documentation label Sep 16, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

No branches or pull requests

2 participants