Using Git in an (un)orthodox way in your team
summary
Team rules cover exact commit message formats, branching model and enforced pre-commit hooks, plus protected branches and SSH vs HTTPS token hygiene. Git usage notes show that spending seconds daily on git rebase avoids hours of merge conflict recovery, and that reflog can rescue accidental force-pushes. Repository repair uses git sizer to find oversized blobs and BFG Repo-Cleaner or git-lfs to remove large binaries, but rewriting history forces everyone to reclone.
AI-written summary · about
chapters (12)
- 0:00Unorthodox Git usage
- 3:18Git as distributed VCS
- 6:30Local Git setup best practices
- 9:23Branching strategy for teams
- 10:07Committing with meaningful messages
- 12:36Reviewing pull requests kindly
- 14:08Handling temporary changes with stash
- 15:11Power and caution of rebase
- 16:59Avoiding bloated repos
- 18:46Binary files and Git LFS
- 19:07Searching multiple repos
- 20:35Team collaboration tips
