docs: Document commit-all flag with example #127
Conversation
|
|
||
| If you want to commit generated artifacts in the release commit (e.g. [#96](https://github.com/conventional-changelog/standard-version/issues/96)), you can use the `--commit-all` or `-a` flag. You will need to stage the artifacts you want to commit, so your `release` command could look like this: | ||
|
|
||
| ```json |
There was a problem hiding this comment.
might be good to provide an example of a command that might produce the artifacts, .e.g.,
prerelease: "webpack -p --bail"
There was a problem hiding this comment.
I think the link to the issue should suffice :) unless there's more support for it I'll leave it as is.
There was a problem hiding this comment.
I'm with @bcoe I would add the prerelease script for context. Otherwise this looks good. IMHO it's better to give that one more line of context when people are not that likely to follow a link to a lengthy conversation.
There was a problem hiding this comment.
One question though, should I leave the link to the issue in?
There was a problem hiding this comment.
Sure, I don't think there's any real reason not to. We can remove it if someone deems it "unstylish" 😄 . Thanks!
|
|
||
| If you want to commit generated artifacts in the release commit (e.g. [#96](https://github.com/conventional-changelog/standard-version/issues/96)), you can use the `--commit-all` or `-a` flag. You will need to stage the artifacts you want to commit, so your `release` command could look like this: | ||
|
|
||
| ```json |
There was a problem hiding this comment.
I'm with @bcoe I would add the prerelease script for context. Otherwise this looks good. IMHO it's better to give that one more line of context when people are not that likely to follow a link to a lengthy conversation.
|
@Tapppi ready to go! |
|
Merging this as @bcoe already approved it too. |
Resolves #96.
@Tapppi @bcoe please take a look :)