| English | 中文 |
This directory is intended for tech leads and team maintainers. Its goal is to configure GitHub from just a code hosting tool into a core part of collaboration, review, CI, release, security, and auditing.
It belongs to the “manage collaboration” layer of the knowledge map and turns a team’s collaboration decisions into repository and platform rules.
| Problem to Solve | Recommended Reading |
|---|---|
| Want to establish a complete view of repository governance | GitHub Engineering Governance |
| Want to see the enterprise collaboration configuration stack at once | Enterprise GitHub Workflow Stack |
| Want to protect main or release branches | Branch Protection |
| Want to unify rules across multiple repositories | Rulesets |
| Key directories require owner review | CODEOWNERS |
| Too many PRs, main branch breaks frequently on merge | Merge Queue |
| AI agents are starting to push code and need governance rules | AI Agent Governance |
Teams with multiple repositories should prioritize Reusable Workflows to avoid configuration drift caused by copying CI setups per repository. Teams with fixed release windows, hotfixes, and release notes should prioritize Release Management.
If the team has already placed configurations, infrastructure, and release strategies into the repository, these two articles should be read together.