[chore] Document area ownership auto-close behavior#3760
Open
cijothomas wants to merge 3 commits into
Open
Conversation
…NG.md and AREAS.md
cijothomas
changed the title
cijothomas
changed the title
cijothomas
changed the title
jsuereth
reviewed
May 29, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Documents and improves the auto-close behavior introduced in #2835 so contributors are not caught by surprise.
CONTRIBUTING.md: new### Area ownership checksubsection under## Automation(+ TOC update).AREAS.md: short callout above the table linking to the contributing guide..github/scripts/triage/check-changes-ownership.ts: rewrite the auto-close comment to be friendlier — explicitly say the contribution is welcome, point to the bugfix-reopen procedure, the new-SIG process, and the Slack channel.Context: #3759 was auto-closed even though
AREAS.mdsays bugfixes are welcome for the HTTP area. The behavior was not documented anywhere a contributor would naturally look, and the bot comment was terse.