Maintainers
This document explains who maintains My Git Handbook and how maintenance decisions are made.
Primary Maintainer
- GitHub: @xirong
- Role: primary maintainer, content owner, release owner
Maintainer Responsibilities
The primary maintainer is responsible for:
- Reviewing pull requests
- Triaging issues
- Maintaining the roadmap
- Keeping documentation links healthy
- Publishing releases
- Preserving the project direction
- Reviewing AI-native development content for practical value
- Keeping templates and workflow guidance usable for real engineering teams
Review Policy
Small fixes can be merged quickly when they are clearly correct:
- Typo fixes
- Broken link fixes
- Formatting fixes
- Small wording improvements
Larger changes should usually start with an issue:
- New guides
- Major rewrites
- New company practice cases
- Workflow recommendations
- Changes to project structure
- License or governance changes
Release Policy
Releases are used to mark meaningful handbook milestones, such as:
- New major content sections
- Documentation governance updates
- Template improvements
- Link quality improvements
- AI-native workflow updates
Patch releases can be used for maintenance improvements that make the project easier to contribute to or maintain.
Contribution Expectations
Contributors should keep changes focused, include validation notes, and avoid adding unsourced recommendations. When a guide describes Git or GitHub behavior, official documentation or primary sources are preferred.