-
Notifications
You must be signed in to change notification settings - Fork 762
Description
Affected Packages
@changesets/cli
Problem
We recently migrated to Changesets and are seeing some issues related to the commit option being used by both add and version commands. We set it to true, thinking that it would be convenient if didn't have to run git add/commit immediately after having run changeset add. But when the action/changesets picks up the changes and runs changeset version, it adds [skip ci] to the commit message and submits the PR. When we merge the PR, nothing happens because CI is skipped.
I looked through the docs and even looked into the code to see if I had missed a configuration somewhere, but it turns out it was removed back in 2.0, with the message below:
- If you use
commitandskipCIinversionOptionsorpublishOptions, set commit totrue, all commits will include a skip ci message. if you have a use case for only using commit on one command or not including a skip ci message by default, contact us and we will talk about re-implementing these features.
So I guess what I'm asking is if we can re-implement this feature 😄
Proposed solution
Ability to override commit for one command, or at least split up the commit option so we can set different values for add and version commands.