Git Branches: Intuition and Reality
1–10 of 281 posts
Re: Git Branches: Intuition and Reality
#2This is worth an essay of its own.
Re: Git Branches: Intuition and Reality
#3 git pull
git merge x
git checkout [-b] foo
git commit
git pushRe: Git Branches: Intuition and Reality
#4I cannot be the only one that gets away with only knowing: git pull git merge x git checkout [-b] foo git commit git push
Re: Git Branches: Intuition and Reality
#5I cannot be the only one that gets away with only knowing: git pull git merge x git checkout [-b] foo git commit git push
Re: Git Branches: Intuition and Reality
#6I cannot be the only one that gets away with only knowing: git pull git merge x git checkout [-b] foo git commit git push
(well... it's about 1% because I do everything using the eclipse git UI, but that's the same behavior you get from that commands)
Re: Git Branches: Intuition and Reality
#7I cannot be the only one that gets away with only knowing: git pull git merge x git checkout [-b] foo git commit git push
Re: Git Branches: Intuition and Reality
#8One example that also bites people: moving files isn't stored in git - if you move files (even with `git mv`) and create a new commit, the moves aren't stored, but this is reconstructed later by the client based on similarity, which comes from the diff algorithm.
And git has multiple diff algorithms to pick from: https://git-scm.com/docs/git-config#Documentation/git-config...
And optionally to not detect renames in diff output with `diff.renames`: https://git-scm.com/docs/git-config#Documentation/git-config...
Re: Git Branches: Intuition and Reality
#9I cannot be the only one that gets away with only knowing: git pull git merge x git checkout [-b] foo git commit git push
git reset --hardRe: Git Branches: Intuition and Reality
#10I cannot be the only one that gets away with only knowing: git pull git merge x git checkout [-b] foo git commit git push
Basically you can stop using checkout.
*edit*: fixed switch branch creation parameter.