Repository navigation
Conversation
Team labels map to R&D groups, so the right writer gets pulled in even on fork PRs, without relying on CODEOWNERS paths.
Contributor
|
✅ Preview for this PR (commit |
Matches CODEOWNERS, so writers aren't pinged on drafts or closed PRs.
The PR toolkit skips authors outside Product Engineering, so about half of outside docs PRs get no team label and no writer.
Contributor
|
My teams look okay (even though this is the first time I hear of c&c 🤨). One question, wouldn't it make sense to limit the check to files that live in |
Contributor
Author
|
I think c&c is a legacy label and could be removed tbh... 🤔 Oh yeah that is a good point as well I think I was erring on the side of being cautious to catch also changes to skills, agent files, standards but those are rarely if ever changed by someone else than us so I guess limiting it to |
This branch has not been deployed
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
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.
Adds a workflow that requests a technical writer's review when a PR gets a team label (
t-*), so the writer for that team's R&D group is pulled in automatically, including on fork PRs, instead of depending on CODEOWNERS paths.It runs on
pull_request_target(labeled,ready_for_review), maps each label to Foundation, Creators or Integrators and requests that group's writer, ignores unmapped labels, and skips the request when the writer is the PR author. Like CODEOWNERS, it waits until a draft is ready for review and leaves closed PRs alone.The PR toolkit only labels PRs from Product Engineering members, so a fallback job requests @TC-MO for triage when no writer has been requested 90 seconds after a PR opens or becomes ready. It skips bots and PRs from writers.