- Self Introduction
- Interrupt if you have questions!
- Source Code Version Control
- Historical record of changes
- Source Distribution
- Communication
- To your team
- To your future self
- To the team maintaining this project long after you have gone
git log -p
git blame
- Stop running
git commit -m
- A useful commit message:
- A summary, written impertively and no longer than 50 characters
- A detailed message, each line no longer than 72 characters
- Why is this change necessary?
- How does this address the issue?
- What side effects does this change have?
- References and resources
- Commit logically-related changes together
git add --patch
Create a commit template ~/.gitcomittemplate
# Why is this change necessary?
# How does it address the issue?
# What side effects does this change have?
# References
- Setup your ~/.gitconfig
- Set your preferred editor
- Stop running
git commit -m
- Use lots of small feature branches
- At least one branch per ticket
- Don't make people pull your code
- Be liberal with images and gifs
- Add ticket URLs
- Do them in person, or over the phone, or when you have a free moment, or just be nice