Skip to content

Ability to set commit to different values in add and version commands. #688

@tido64

Description

@tido64

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:

  1. If you use commit and skipCI in versionOptions or publishOptions, set commit to true, 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.

https://github.com/atlassian/changesets/blob/678b16a6e49976bd3884919303bc22ed6690d151/packages/cli/CHANGELOG.md?plain=1#L738

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.

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions