-
Notifications
You must be signed in to change notification settings - Fork 7
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
Add versioning branches or tags #5
Comments
WDYT of using Nx (to be consistent with woocommerce/woocommerce stack) and https://github.com/jscutlery/semver plugin? nx run storybook:version --releaseAs=minor To do version bumps, git commit, tag ( |
I guess is same as NPX? Glad to use it, looks cool and I wanted to give it a go for a long time. So 👍 for it
Never used it. (Neither heard about it) Wouldn't be enough with git flow? |
not really npx (at least the one I know of) is an npm package that gives a command to execute binaries. While Nx is a rather big tool to setup a monorepo workflows.
I don't think git flow works for monorepos out of the box. But maybe there is a way to use git flow directly with Nx. I don't know, As I've never used Nx or |
Maybe we can wait with Nx setup for woocommerce/woocommerce#33079 as if Woo will move away to another tool, I'd use here the same. |
instead of relative FS path, to make the `jsdoc` package installable elsewhere. Related to #5 Address #10 (comment)
User story
As a developer I want to refer to this repo using versioned tags instead of "trunk" branch.
How to reproduce the problem
For referring to this repo we should add the branch trunk.
Describe the solution you'd like
Use a release version like WooCommerce or other repos in do.
Acceptance criteria
The text was updated successfully, but these errors were encountered: