GV

GeezerVison

The World Wide Web, restored to 800 pixels of glory.

Home|About|Gaming cabinet|Archives|How it works|Starter sites

On this site

  • Sign in
  • ActionsCI/CD and automation
  • CodespacesCloud development environments
  • All Features
  • Documentation
  • Training
  • Certifications
  • Build with Copilot
  • Customize Copilot
  • Integrations
  • Trending repos
  • GitHub Sponsors
  • Developer articles
  • Enterprises

This view

  • Original page
  • New address

GeezerVison is showing github.com — changesets/docs/checking-for-changesets.md at main · codapult/changesets

Expand file tree

/

checking-for-changesets.md

Copy path
More file actions
More file actions

Latest commit

 

History

History
History
14 lines (10 loc) · 816 Bytes
/

checking-for-changesets.md

Copy path

File metadata and controls

14 lines (10 loc) · 816 Bytes
Raw
Copy raw file
Download raw file
Edit and raw actions

Warning

This documentation is outdated. View the up-to-date version at https://changesets.dev/guide/automating#how-do-i-ensure-pull-requests-have-changesets

Checking for changesets

Using @changesets/cli, there is a status command. See the docs for it in the @changesets/cli readme

We have a github bot and a bitbucket addon that alert users of missing changesets.

If you want to cause a failure in CI on missing changesets (not recommended), you can run changeset status --since=main, which will exit with a status code of 1 if there are changed packages but no new changesets. It will not fail if there are no changed packages.

You are visitor 01402520 — GeezerVison does not store the pages you look up.
Best viewed with Netscape Navigator 4.7 or Internet Explorer 6 at 800×600. No cookies required.