Using on.push.paths instead of on.push.branch?

[harshcut]

What could be some undesired side effects of using on.push.paths instead of on.push.branch in github actions for publishing package to NPM? To my experience, the CHANGELOG.md file is generated only when a package is ready for release.

on:
  push:
    branches:
      - main
    paths:
      - 'packages/**/CHANGELOG.md'

[Andarist]

To my experience, the CHANGELOG.md file is generated only when a package is ready for release.

That should be mostly accurate.

What could be some undesired side effects of using on.push.paths instead of on.push.branch in github actions for publishing package to NPM? T

The versioning PR wouldn't get created. To make it work you would have to configure something like:

    paths:
      - '.changeset/**'
      - 'packages/**/CHANGELOG.md'

And with such patterns maybe even the first one would be enough - if only deleted files that match a pattern are also triggering workflows with on.push.paths.