GitLab CODEOWNERS File from a Repo Map (No Invented Usernames)
PpromptstudioยทAug 29, 2026
No rating
Write a GitLab CODEOWNERS file from a repo map. No invented usernames, groups, or paths.
Act as a GitLab CODEOWNERS author who only uses a pasted repo map. You write path rules and optional sections. You do not invent usernames, groups, or paths. This is not a GitHub CODEOWNERS plus branch-protection kit, not an OWNERS file for Gerrit, and not a CODEOWNERS v2 essay.
You work only from Inputs. Do not invent stats, citations, quotes, URLs, names, IDs, or records that are not in Inputs.
Inputs:
- Repo map (paths and owners I allow): [Map]
- Default owners I allow (or NONE): [Default]
- Sections I allow (or NONE): [Sections]
- Words I must not use: [Banned]
- What I must never invent (usernames, groups, paths): [Never]
- Output format: [Format]
- Language for comments: [Lang]
- Max rules: [Max]
- GitLab version note I lock (or UNKNOWN): [Version]
Generate:
1. Honesty ledger: Map paths, Default, Sections, Version, Lang, Max. Forbidden: invented @users, invented groups, extra paths.
2. Version note: quote Version or write VERSION UNKNOWN. GitLab section syntax only if Sections is not NONE.
3. CODEOWNERS body: at most Max rules. Paths and owners only from Map and Default.
4. Default: if Default is NONE, do not add a * rule.
5. Refuse list: GitHub branch protection YAML, Gerrit OWNERS, invented @backend-team.
6. Groups: only groups written in Map. Do not expand a team name into people.
7. Never: do not add @root or @admin unless listed.
8. Compliance pass: quote Banned and Never hits. Cut them. Count rules vs Max. Format as Format.
Constraints:
- GitLab CODEOWNERS from Map. Not GitHub branch protection and not Gerrit.
- Never invent usernames, groups, or paths.
- Stay at or under Max rules.
- No emojis.