Roadmap
This roadmap describes how My Git Handbook will continue evolving as a practical Git/GitHub handbook for modern engineering teams and AI-native development workflows.
v2.0 Direction
The v2.0 line focuses on turning the repository into a maintained handbook with clear learning paths, operational playbooks, reusable templates, bilingual content, and documentation quality checks.
Core themes:
- Git fundamentals and mental models
- Daily developer workflows
- Team collaboration models
- GitHub engineering governance
- AI-native Git workflows
- Troubleshooting and recovery playbooks
- Large repository practices
- Reusable templates
- Company practice case studies
v2.0.1
The v2.0.1 maintenance release focuses on open source project governance and maintainability.
v2.1.0
The v2.1.0 release focuses on agent governance and agent-facing conventions, so the handbook covers AI agents as first-class repository participants.
Next Maintenance Areas
Documentation Quality
- Improve English prose in high-traffic guides
- Keep Chinese and English navigation aligned
- Expand link checking for external links where practical
- Review old resources and mark outdated material clearly
AI-Native Development
- Refine AI-generated code review guidance
- Add more realistic AI diff review examples
- Improve stacked PR guidance for AI-generated changes
- Collect practices from Codex, Claude Code, Cursor, Aider, and GitHub Copilot workflows
GitHub Engineering Governance
- Expand Rulesets examples
- Improve branch protection examples
- Add more reusable GitHub Actions patterns
- Add clearer release and rollback playbooks
- Label issues for broken links, wording fixes, and new guide requests
- Encourage small pull requests
- Review community examples before adding them as recommended practice
- Keep issue triage and release notes visible
Maintenance Principles
- Prefer real-world problems over generic tutorials.
- Prefer safe recovery paths over command lists.
- Prefer small, reviewable pull requests.
- Prefer official documentation and primary sources.
- Keep historical resources available, but do not present outdated content as the primary path.