git_for_devops/12-codeowners.txt at main · path4cloud2024/git_for_devops · GitHub

1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
34
35
36
37
38
39
40
41
42
43
44
45
46
47
48
49
50
51
52
53
54
55
56
57
👥 CODEOWNERS File – Explained + Sample

The CODEOWNERS file defines who must review changes for specific files or directories.

📍 Location:
    .github/CODEOWNERS
    (or root: CODEOWNERS)

✅ Sample CODEOWNERS File (Production-ready)

# Default owner for everything
* @platform-team

# Backend application code
/app/ @backend-team

# Frontend code
/frontend/ @frontend-team

# Infrastructure & DevOps
/infra/ @devops-team
/terraform/ @devops-team
/k8s/ @devops-team

# CI/CD pipelines
/.github/workflows/ @devops-team

# Security-related files
/security/ @security-team
*.pem @security-team
*.key @security-team

# Documentation
/docs/ @tech-writers
README.md @tech-writers


##########################################
🧠 How CODEOWNERS Works
        Example scenario:
            PR modifies files in /infra/
            GitHub automatically:
            Requests review from @devops-team
            Blocks merge until at least one DevOps member approves
            Even if:
                ✔ CI passed
                ✔ Other reviewers approved

    👉 Code Owner approval is mandatory

🔐 Why CODEOWNERS is important
| Benefit    | Why it matters                  |
| ---------- | ------------------------------- |
| Ownership  | Clear responsibility            |
| Security   | Prevents unauthorized changes   |
| Expertise  | Right people review the code    |
| Governance | Mandatory for infra & prod code |