-
Notifications
You must be signed in to change notification settings - Fork 6.3k
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
chore: configuration for merge queues #5592
Conversation
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
📦 Next.js Bundle Analysis for nodejs.orgThis analysis was generated by the Next.js Bundle Analysis action. 🤖 This PR introduced no changes to the JavaScript bundle! 🙌 |
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.
I've read through the merge queue docs a couple times and am excited to try this out!
cc @nodejs/website fast-tracking this as this should be a simple enough change? React with 👍 for approval! |
Merge Queues Enabled! (And Enforced on |
Description
As I'm discussing with @bmuenzenmeyer we're thinking in using merge queues to reduce the noise of merge commits and etc on PRs.
This PR updates our GitHub Actions to be compatible with Merge Queues
cc @bmuenzenmeyer