Establish tiered CODEOWNERS for enterprise-access#120
Draft
Conversation
Agent-Logs-Url: https://github.com/edx/enterprise-access/sessions/d05bd4a9-968a-425c-b872-16722c4e3147 Co-authored-by: macdiesel <67862+macdiesel@users.noreply.github.com>
Copilot
AI
changed the title
[WIP] Add CODEOWNERS file for tiered code review
Establish tiered CODEOWNERS for enterprise-access
Apr 1, 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
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.
Replaces the flat single-rule CODEOWNERS (all teams on everything) with a three-tier ownership model aligned to the contractor access rollout policy.
Ownership tiers
*) —@edx/enterprise-titansonly; backstop for any path not matched below/enterprise_access/) — Titans +@edx/enterprise-sunrise-maintainers+@edx/enterprise-lakshy-maintainers; uses trusted maintainer subteams so only designated engineers (not the full contractor team) can satisfy CODEOWNERS review/docs/,*.md,*.rst) — Titans + full@edx/enterprise-sunrise+@edx/enterprise-lakshy; lower-risk content where broader contractor participation is acceptableOriginal prompt
Problem / Goal
Establish a
.github/CODEOWNERSfile foredx/enterprise-accessto enforce tiered code review and merge permissions for contractor subteams, following the finalized company access model:Requirements
.github/CODEOWNERS(creating directory/file if needed).* @edx/enterprise-titans/enterprise_access/ @edx/enterprise-titans @edx/enterprise-sunrise-maintainers @edx/enterprise-lakshy-maintainers(assuming main code is in enterprise_access/)/docs/ @edx/enterprise-titans @edx/enterprise-sunrise @edx/enterprise-lakshy*.md @edx/enterprise-titans @edx/enterprise-sunrise @edx/enterprise-lakshy*.rst @edx/enterprise-titans @edx/enterprise-sunrise @edx/enterprise-lakshymain.Acceptance criteria
The following is the prior conversation context from the user's chat exploration (may be truncated):
User: I"ve been working on this plan with chat GPT. What do you think?
Below is a Claude-ready implementation plan you can paste into Claude (or use as a task brief). It includes: team definitions, repo list + URLs, the policy intent, the exact CODEOWNERS templates to create, and the branch protection / permissions checklist.
Implementation Plan: Phased Merge Autonomy for Enterprise Repos (Claude Task Brief)
Date: 2026-04-01
Goal: Gradually delegate PR review + merge autonomy to contractor teams while keeping a “master” team with full approval/merge authority across all enterprise repos.
1) Organizations in scope
openedxedx2) Teams (existing)
These teams already exist and must be used as the starting point:
2.1 Master / can do everything
enterprise-titans2.2 Newly onboard teams (can open PRs)
enterprise-sunriseenterprise-lakshy2.3 Ownership by domain
enterprise-lakshyowns:enterprise-sunriseowns:3) Repositories in scope (high priority for CODEOWNERS)
Microservices / Backend Services
Frontend Applications
This pull request was created from Copilot chat.