-
Notifications
You must be signed in to change notification settings - Fork 19
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Do not comment on some PRs, based on private packages or changed path? #39
Comments
I guess this is kind of related with #11.
But it does not work well with the case where one has a monorepo where only some of the packages under the monorepo are actually published to npm and intended to be under controll of the changesets bot. My thought here is that some architecture changes to how the bot should behave must be done to accomplish this feature. |
+1 to this feature, we have a monorepo where packages are marked This seems in line with |
Hello! We're using changeset for Astro and are loving it so far. However, we have some workspace "packages" that aren't really packages. The docs site, the www homepage, and some example directories are all included in our workspace (with
"private": true
).Is it possible to configure the bot to not comment on those PRs? It is distracting for our users who think they need a changeset added, when in reality we do not usually bump these packages.
Alternatively, is there any condition where the bot doesn't trigger on a new PR that we could leverage? Happy if there is some workaround that we could use.
Example PR: withastro/astro#1042
The text was updated successfully, but these errors were encountered: