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

Option to disable the git commit #249

Closed
pleunv opened this issue Feb 27, 2018 · 1 comment
Closed

Option to disable the git commit #249

pleunv opened this issue Feb 27, 2018 · 1 comment

Comments

@pleunv
Copy link

pleunv commented Feb 27, 2018

Hey guys! I'm looking into using np in our CI flow but there's one scenario I'm not sure it can currently support.

I would like to set up a CI build inside of a mono-repo that builds each package on every commit and publishes it to NPM but without creating an additional version commit. Packages would be versioned with a timestamp instead of an incrementing build number so this would not be necessary (i.e. package@2.0.0-build.1519722154) and it would create a lot of noise. Within the context of a mono-repo this would also create a commit per package which is definitely not desirable.

This differs from the current suggested --no-publish CI approach as we do want to publish to NPM but not to git, so it's rather an inverse scenario. Would you be open to adding an additional --no-commit or --no-git option to faciliate this? I can dig in the code and prepare a PR if so.

@sindresorhus
Copy link
Owner

#250 (comment)

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