{"id":40,"date":"2023-11-20T11:07:58","date_gmt":"2023-11-20T10:07:58","guid":{"rendered":"https:\/\/www.huwig.de\/en\/?p=40"},"modified":"2023-11-20T11:07:58","modified_gmt":"2023-11-20T10:07:58","slug":"handy-git-tricks","status":"publish","type":"post","link":"https:\/\/www.huwig.de\/en\/de\/2023\/11\/20\/handy-git-tricks\/","title":{"rendered":"Handy Git tricks"},"content":{"rendered":"
\n
\n

This is a collection of tricks I use to make my life with Git easier while maintaining a clean history that helps to understand the code. Which is the whole point of version control, isn’t it?<\/p>\n

Transplant a branch<\/h1>\n

\"\"<\/a>To transplant a Git branch from one branch to another, use<\/p>\n

git rebase --onto<\/pre>\n
Example<\/h2>\n
git rebase --onto beta develop fix<\/pre>\n
Update without checkout<\/h1>\n
\"\"<\/a><\/p>\n
To update a branch without checking it out first – e.g. to rebase onto the latest version of the parent branch, use<\/p>\n
git fetch origin <branch>:<branch><\/pre>\n
You really need to type the target branch twice!<\/p>\n
Example<\/h2>\n
git fetch origin develop:develop<\/pre>\n
Rewrite history<\/h1>\n
Before I merge I rewrite my history so that each commit is clean and there are no „changes after review“ commits: they don’t help to understand why the code is the way it is.<\/p>\n
git add .\r\ngit commit --fixup\r\ngit rebase -i --autosquash develop<\/pre>\n
Read more about this in the Git Book<\/a><\/p>\n
Know the version<\/h1>\n
We use annotated tags to mark each release. We also never merge back but only merge older branches into newer branches. This allows us to easily determine the version number based on the tags.<\/p>\n
git describe --first-parent [branch]<\/pre>\n
If you don’t give the name of a branch (or hash or similar), you get the version number of the current branch.<\/p>\n
Example<\/h2>\n
git describe --first-parent beta<\/pre>\n<\/div>\n<\/div>\n","protected":false},"excerpt":{"rendered":"
This is a collection of tricks I use to make my life with Git easier while maintaining a clean history that helps to understand the code. Which is the whole point of version control, isn’t it? Transplant a branch To transplant a Git branch from one branch to another, use git rebase –onto Example git … Handy Git tricks<\/span> weiterlesen<\/a><\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"inline_featured_image":false,"footnotes":""},"categories":[1],"tags":[],"class_list":["post-40","post","type-post","status-publish","format-standard","hentry","category-allgemein"],"_links":{"self":[{"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/posts\/40","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/comments?post=40"}],"version-history":[{"count":1,"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/posts\/40\/revisions"}],"predecessor-version":[{"id":41,"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/posts\/40\/revisions\/41"}],"wp:attachment":[{"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/media?parent=40"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/categories?post=40"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.huwig.de\/en\/wp-json\/wp\/v2\/tags?post=40"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}