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

Recommend correct branch for repositories with non-master defaults? #184

Closed
tmcw opened this issue Jun 1, 2017 · 3 comments
Closed

Recommend correct branch for repositories with non-master defaults? #184

tmcw opened this issue Jun 1, 2017 · 3 comments

Comments

@tmcw
Copy link
Contributor

tmcw commented Jun 1, 2017

Working in a repository in which gh-pages is the main / only branch, the recommended publishing step:

git push --follow-tags origin master; npm publish

Will always fail, because master is not a valid branch. Could standard-version check for the main branch and recommend it?

@stevemao
Copy link
Member

stevemao commented Jun 3, 2017

Could standard-version check for the main branch and recommend it?

Probably should check the current branch (which is where the command is running from and its most likely your release branch), and print it's name.

@tobiasbueschel
Copy link

Thanks for raising this issue ticket @tmcw 👌I also have a similar use case.

On the same note, it would also be nice if there was a way of suppressing standard-version from printing npm publish or customising the success message altogether.

Some projects might not need to run npm publish locally as the command might already be part of the CI/CD pipeline.

@tmcw
Copy link
Contributor Author

tmcw commented Dec 26, 2020

Fixed in #331!

@tmcw tmcw closed this as completed Dec 26, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Development

No branches or pull requests

3 participants