-
Notifications
You must be signed in to change notification settings - Fork 47.9k
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
bot for pr notifications #31985
bot for pr notifications #31985
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
Comparing: e0c893f...21ae3fb Critical size changesIncludes critical production bundles, as well as any change greater than 2%:
Significant size changesIncludes any change greater than 0.2%: Expand to show |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
What do you think of only creating these notifications once PRs are marked as ready for review? This could allow "pinging" the channel again by marking PRs as draft/ready-for-review again which doesn't sound too bad?
fe6f4ba
to
0f157c4
Compare
@eps1lon not sure anyone really uses the 'ready for review" workflow. The goal here is to mirror the bot we've used for years internally |
@eps1lon ready for review! lol |
Going to take some testing to get this right