Git conventions and best practices
This part of the documentation describes how Git and related concepts are used across projects.
Debate about the βrulesβ stated below is expected and welcomed - conventions should evolve with the team.
The goal is to keep:
- History readable
- Changes reviewable
- Releases predictable
- Collaboration low-friction
ποΈ General recommendation
- Pull often
ποΈ Branches
Naming convention
ποΈ Commit standards
Content
ποΈ Pull request
Pull Requests (PRs) are the only way code is merged into master/main.
ποΈ Versioning scheme
Packages follow Semantic Versioning for tag naming.
ποΈ Git Advance Tricks Examples
2 items