You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
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. [email protected]) 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.
The text was updated successfully, but these errors were encountered:
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.
[email protected]
) 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.The text was updated successfully, but these errors were encountered: