Good Team Habits
Names, sizes and messages.
Tools only get you so far. Teams that work well with Git share a few simple habits. None of them are hard, and they make a huge difference.

- Tools only go so far
- A few shared habits
- Small things, big difference
Branch names
Give branches short names that say what they're for. Many teams start with a type, then a slash. Feature slash dark mode. Fix slash broken link. Docs slash readme. Anyone can tell what a branch is about, just from its name.
| key | value |
|---|---|
| feature/dark-mode | new feature |
| fix/broken-link | bug fix |
| docs/readme | documentation |
| Lowercase | words joined with dashes |
Small pull requests
Keep pull requests small. A pull request with fifty changed lines gets a careful review in minutes. One with two thousand lines gets a quick, looks good to me, and bugs slip through. Small pull requests are reviewed faster, merged sooner, and cause fewer conflicts.
Summary
Clear branch names, small pull requests, and good messages keep a team fast and friendly. Next, a tour of a GitHub repository page.
Key takeaways- type/short-name branches
- Small pull requests
- Clear commit messages