git stores diffs
commits as snapshot in time
revert a file or the whole project
git project is called a repo
lab notebook for code
commits are linear chain of edits
a branch is an alternative timeline of commits
can merge branches back together
Unlimited undo
snapshots come with user data "blame" and description
good for working in distributed teams or sharing code
licenses
create and clone
merge squash rebase
When to fork vs clone
Notes to include:
git stores diffs commits as snapshot in time revert a file or the whole project git project is called a repo lab notebook for code commits are linear chain of edits a branch is an alternative timeline of commits can merge branches back together Unlimited undo snapshots come with user data "blame" and description good for working in distributed teams or sharing code licenses create and clone merge squash rebase When to fork vs clone