|
|
|
Download from: https://git-scm.com/
|
|
|
|
|
|
|
|
RTFM: https://git-scm.com/book/en/v2
|
|
|
|
## Documentation and tutorials
|
|
|
|
|
|
|
|
Conventional Commits (specification for meaningful commit messages): https://www.conventionalcommits.org/en/v1.0.0/ |
|
|
\ No newline at end of file |
|
|
|
* RTFM: https://git-scm.com/book/en/v2
|
|
|
|
* Conventional Commits (specification for meaningful commit messages): https://www.conventionalcommits.org/en/v1.0.0/
|
|
|
|
* GitKraken "learn git" stuff: https://www.gitkraken.com/learn/git
|
|
|
|
|
|
|
|
## Git best practices
|
|
|
|
|
|
|
|
(from https://about.gitlab.com/topics/version-control/version-control-best-practices/)
|
|
|
|
|
|
|
|
* Make incremental, small changes (less likely to cause merge issues)
|
|
|
|
* Keep commits atomic (makes reverts easier)
|
|
|
|
* Develop using branches (to keep a main branch clean and stable)
|
|
|
|
* Write descriptive commit messages (see also conventional commits above)
|
|
|
|
* Obtain feedback through code reviews (probably less doable / important for us, although may be useful sometimes)
|
|
|
|
* Identify a branching strategy. The most common being:
|
|
|
|
* Centralized: everyone on one branch
|
|
|
|
* Feature branching: one feature = one branch, merge to main when feature is stable and close branch
|
|
|
|
* GitFlow: develop branch -> release branch -> main branch (more details [here](https://www.gitkraken.com/learn/git/git-flow))
|
|
|
|
* Personal branching: one person = one branch, merge to main when feature is stable and keep working on next feature in same branch. |
|
|
\ No newline at end of file |
