File tree Expand file tree Collapse file tree
docs_build/dev/ProjectInstructions/team_assignments Expand file tree Collapse file tree Original file line number Diff line number Diff line change 11# TEAM_ASSIGNMENTS
22
3+ # Active Team Registry
4+
5+ | Team | Assignment | Branch | PR | Status |
6+ | --------| --------| --------| --------| --------|
7+ | Team OWNER | Active Team Registry | pr/26172-OWNER-024-active-team-registry | PR_26172_OWNER_024-active-team-registry | Active |
8+
9+ Rules:
10+ - Registry is the authoritative active-work view.
11+ - Registry must match ` TEAM_ASSIGNMENTS.md ` .
12+ - Registry must be updated when assignments change.
13+ - Registry must be updated when branches are retired.
14+ - Registry must be updated when PRs merge.
15+ - Teams with no active work are omitted.
16+
17+ A team is Active when:
18+ - it has an assigned backlog item
19+ - or it owns an active branch
20+ - or it owns an active draft/open PR
21+
22+ A team is not listed in Active Team Registry when:
23+ - it has no assignment
24+ - it has no active branch
25+ - it has no active PR
26+
27+ Result:
28+ If a team is missing from Active Team Registry:
29+ it is currently inactive.
30+
331## Assignment Status Legend
432
533- Available: team may pull one ` [ ] ` backlog item when explicitly instructed.
@@ -32,11 +60,11 @@ Active branch: none.
3260
3361## Team OWNER
3462
35- Status: Available
63+ Status: Active
3664
37- Active assignment: none .
65+ Active assignment: Active Team Registry .
3866
39- Active branch: none .
67+ Active branch: pr/26172-OWNER-024-active-team-registry .
4068
4169## Team Name Registry
4270
You can’t perform that action at this time.
0 commit comments