Skip to content

feat(governance): add general PR policies#112

Open
avivkeller wants to merge 3 commits into
nodejs:mainfrom
avivkeller:patch-11
Open

feat(governance): add general PR policies#112
avivkeller wants to merge 3 commits into
nodejs:mainfrom
avivkeller:patch-11

Conversation

@avivkeller

Copy link
Copy Markdown
Member

Fixes #97
Fixes #98

As discussed in today's meeting with @bmuenzenmeyer

Added policies for pull requests, including atomic changes and fast-track approvals.
Copilot AI review requested due to automatic review settings March 16, 2026 19:41

Copilot AI left a comment

Copy link
Copy Markdown
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds governance text to formalize pull request expectations for the Node.js Web Team, addressing fast-track approvals and PR scope/relevancy.

Changes:

  • Introduces an “Atomic Pull Requests” policy to encourage single-purpose PRs.
  • Updates the “Fast-Track Policy” to require approval from someone other than the author and fast-track requester, with an exception path for urgent changes.

💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.

You can also share your feedback on Copilot code review. Take the survey.

Comment thread GOVERNANCE.md Outdated
Comment thread GOVERNANCE.md
@avivkeller

Copy link
Copy Markdown
Member Author

Should I also document our auto-merge policy?

@MattIPv4

Copy link
Copy Markdown
Member

Should I also document our auto-merge policy?

I don't think so, I'm not sure we have a policy there, it is just safe automation around our regular merge policy?

@MattIPv4 MattIPv4 left a comment

Copy link
Copy Markdown
Member

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Putting an explicit block on this as I would like to make sure I have the time to review this once I'm back from adventuring

@avivkeller

Copy link
Copy Markdown
Member Author

Should I also document our auto-merge policy?

I don't think so, I'm not sure we have a policy there, it is just safe automation around our regular merge policy?

Yes, to clarify, I meant noting that for non-fork PRs, that label is also an option

@MattIPv4

Copy link
Copy Markdown
Member

Yes, to clarify, I meant noting that for non-fork PRs, that label is also an option

Ah. Sure!

Comment thread GOVERNANCE.md
Comment thread GOVERNANCE.md
@avivkeller avivkeller requested a review from MattIPv4 June 8, 2026 19:08
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

Update our policies on relevancy Require secondary approval for fast-track

7 participants