Changesets ignoring the skipCI config key

Affected Packages

pkg:cli

Problem

Setting the config.json this way

{
  "$schema": "https://unpkg.com/@changesets/config@0.3.0/schema.json",
  "changelog": "@changesets/cli/changelog",
  "commit": true,
  "skipCI": false,
  "linked": [],
  "access": "restricted",
  "baseBranch": "master"
}

when changesets commits in CI, the comit message still contains skipCI

Proposed solution

[Noviny]

Had a really quick look into it, and we deprecated the skipCI flag with our version 2 upgrade, as all use-cases where people wanted commit: true, they also wanted skipCI true, and we add the skipCI flag to all our commits.

Happy to leave this open as ‘we should reimplement this to allow fine-grained controls’ but for an immediate fix you can set commit to false and run:

echo "+++ :npm: Publishing to NPM :npm:"
yarn changeset version
git add . && git commit -m "versioned packages"
yarn changeset publish 

My two take-aways from this is we should add skipCI back as its own flag, defaulting to true (what most people have wanted) and fine grain commit so you can set it per command that can commit.

Thanks for raising this!

[jordan-simonovski]

Ah right! Yeah we made a workaround using the manual commit in our CI pipelines. Thanks for doing such a great job on this project!