My team is a mix of front end, back end, and fullstack developers, and we've ended up in a place where one of our monorepos includes a mix of go services, front end apps, and npm packages. In this repo, only the npm packages will be tracked with changesets, as release and versioning is handled separately for the other code.
We tried to turn on the changeset bot in the repo, but for developers not making changes in the npm package folders, the comment was annoying and noisy, so we ended up turning it off. It would be great to restrict the changeset bot to only leave a comment about missing/found changesets when the PR changes are in a tracked package folder. Or, alternatively, to ignore a bunch of folders/files to not trigger a changeset comment from the bot.
My team is a mix of front end, back end, and fullstack developers, and we've ended up in a place where one of our monorepos includes a mix of go services, front end apps, and npm packages. In this repo, only the npm packages will be tracked with
changesets, as release and versioning is handled separately for the other code.We tried to turn on the changeset bot in the repo, but for developers not making changes in the npm package folders, the comment was annoying and noisy, so we ended up turning it off. It would be great to restrict the changeset bot to only leave a comment about missing/found changesets when the PR changes are in a tracked package folder. Or, alternatively, to ignore a bunch of folders/files to not trigger a changeset comment from the bot.