Skip to content

Action that confirms that there is a new changeset entry present for every yarn (classic) workspace that contains provided array of file names.

License

Notifications You must be signed in to change notification settings

Khan/changeset-per-package

Repository files navigation

📦🦋 Changeset Per Package 🦋📦

Test Coverage GitHub Super-Linter CI

This action validates that there is a changeset entry for each package that has been changed.

This repository has two action files:

File Description
./action.yml This composite action calls on other Khan actions to prepare a list of changed files.
./actions/verify-per-package/action.yml This ts action contains its logic to ./src/main.ts. It checks for packages corresponding to changed files, then determines if there is a match for each in changesets.

When Making Changes

Please run yarn all to ensure that it builds and that all tests pass.

This action is dogfooded in the workflow for this repo. See ci.yml. That way, you can test the behavior of your changes by opening a PR.

Usage

You can create version tag(s) that developers can use to reference different stable versions of your action. For more information, see Versioning in the GitHub Actions toolkit.

To include the action in a workflow in another repository, you can use the uses syntax with the @ symbol to reference a specific branch, tag, or commit hash.

steps:
  - name: Checkout
    id: checkout
    uses: actions/checkout@v3

  - name: Verify Changeset Per Package
    id: changeset-per-package
    uses: Khan/changeset-per-package@v1 # Commit with the `v1` tag

About

Action that confirms that there is a new changeset entry present for every yarn (classic) workspace that contains provided array of file names.

Topics

Resources

License

Stars

Watchers

Forks