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
Copy file name to clipboardExpand all lines: README.md
+4-1
Original file line number
Diff line number
Diff line change
@@ -73,7 +73,7 @@ republish it, it would produce the *exact* same hash.
73
73
74
74
### package.json
75
75
76
-
It should be noted that gx is meant to *work with* existing `package.json` files. If you are adding a package to gx that already has a `package.json` file in its root, gx will try and work with it. Any shared fields will have the same types, and any fields unique to gx will kept separate.
76
+
It should be noted that gx is meant to *work with* existing `package.json` files. If you are adding a package to gx that already has a `package.json` file in its root, gx will try and work with it. Any shared fields will have the same types, and any fields unique to gx will kept separate.
77
77
78
78
E.g. A single `package.json` file could be used to serve both gx and another packaging tool, such as npm. Since gx is **Alpha Quality** there may be some exceptions to the above statements, if you notice one, please file an issue.
79
79
@@ -300,6 +300,9 @@ in your `package.json` as your `releaseCmd`. To get the above git commit flow,
300
300
you can set it to: `git commit -a -m \"gx publish $VERSION\"` and gx will
301
301
replace `$VERSION` with the newly changed version before executing the git
302
302
commit.
303
+
In addition to commiting, it will also publish a git tag, using the default command
304
+
`git tag -a "v$VERSION" -m "gx release published as $HASH"`. To change the command you can set
305
+
the `tagCmd` field to a command of your choosing.
303
306
304
307
### Ignoring files from a publish
305
308
You can use a `.gxignore` file to make gx ignore certain files during a publish.
0 commit comments