This post is for people who are already familiar with Git and work on multiple branches (esp. feature branches).
\nBy practice, feature branches are the branches created from a root branch (master or any other as per your branching model) and once feature is complete\/tested – they are merged back into the same root branch.<\/p>\n
\nWorking in such a manner is pretty nice and clean. But things start getting messy if we don’t delete the branches on time (esp. after merging into root branch). In that case when we run command –
\n[groovy]
\n git branch
\n[\/groovy]
\nIt shows us zillions of branches and we start getting feeling to get a rid of all futile branches. But we don’t know which branches are already merged and which are still under progress or yet to be tested.
\n<\/p>\n
Solution to this problem<\/b>:
\n[groovy]
\n # I am assuming that your root branch is master
\n git checkout master
\n git branch –merged
\n[\/groovy]
\n<\/p>\n
Above command will show you all branches which are already merged into the current branch (master branch in this case). This means you can delete these (feature) branches now.
\nFor deleting a branch on local: git branch {-d | D} ‘feature-branch-1’
\nFor deleting from remote: git push origin :feature-branch-1
\nI assumed that origin is your remote.<\/p>\n
Similarly if you run
\n[groovy]
\n git branch –no-merged
\n[\/groovy]
\nIt will give a list of branches which are yet to be merged.<\/p>\n
\nQuestion<\/b>: I got a list of branches which are not merged yet. Now I want to see the commits in particular branch which are not merged into root branch yet?
\nSolution<\/b>:
\n[groovy]
\n git log –pretty=oneline maser..branch1
\n[\/groovy]
\nAgain, master is your root branch. And branch1 is your feature branch having commits yet to be merged.<\/p>\n
Your comments are always Welcome. Please post if you have any!<\/p>\n
Cheers!
\nSalil Kalia
\nSalil [at] IntelliGrape [dot] com
\nTwitter LinkedIn <\/p>\n","protected":false},"excerpt":{"rendered":"
This post is for people who are already familiar with Git and work on multiple branches (esp. feature branches). By practice, feature branches are the branches created from a root branch (master or any other as per your branching model) and once feature is complete\/tested – they are merged back into the same root branch. […]<\/p>\n","protected":false},"author":17,"featured_media":0,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"iawp_total_views":0},"categories":[7],"tags":[375,387],"aioseo_notices":[],"_links":{"self":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/3208"}],"collection":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/users\/17"}],"replies":[{"embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/comments?post=3208"}],"version-history":[{"count":0,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/posts\/3208\/revisions"}],"wp:attachment":[{"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/media?parent=3208"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/categories?post=3208"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.tothenew.com\/blog\/wp-json\/wp\/v2\/tags?post=3208"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}