{"id":30839,"date":"2022-07-24T14:34:53","date_gmt":"2022-07-24T14:34:53","guid":{"rendered":"https:\/\/www.devopsschool.com\/blog\/?p=30839"},"modified":"2022-12-23T05:48:02","modified_gmt":"2022-12-23T05:48:02","slug":"git-tutorial-git-references","status":"publish","type":"post","link":"https:\/\/www.devopsschool.com\/blog\/git-tutorial-git-references\/","title":{"rendered":"Git Tutorial: Git References"},"content":{"rendered":"\n

Branches, remote-tracking branches, and tags are all references to commits. All references are named with a slash-separated path name starting with “refs”; the names we’ve been using so far are actually shorthand:<\/p>\n\n\n\n

1 2 3<\/td>– The branch “test” is short for “refs\/heads\/test”. – The tag “v2.6.18” is short for “refs\/tags\/v2.6.18”. – “origin\/master” is short for “refs\/remotes\/origin\/master”.<\/td><\/tr><\/tbody><\/table><\/figure>\n\n\n\n

The full name is occasionally useful if, for example, there ever exists a tag and a branch with the same name.<\/p>\n\n\n\n

(Newly created refs are actually stored in the .git\/refs directory, under the path given by their name. However, for efficiency reasons they may also be packed together in a single file; see git pack-refs)<\/a>.<\/p>\n\n\n\n

As another useful shortcut, the “HEAD” of a repository can be referred to just using the name of that repository. So, for example, “origin” is usually a shortcut for the HEAD branch in the repository “origin”.<\/p>\n\n\n\n

For the complete list of paths which git checks for references, and the order it uses to decide which to choose when there are multiple references with the same shorthand name, see the “SPECIFYING REVISIONS” section of git rev-parse<\/a>.<\/p>\n\n\n\n

Showing commits unique to a given branch<\/strong><\/h1>\n\n\n\n
\n\n\n\n

Suppose you would like to see all the commits reachable from the branch head named “master” but not from any other head in your repository.<\/p>\n\n\n\n

We can list all the heads in this repository with\u00a0git show-ref<\/a>:<\/p>\n\n\n\n

\n\n\n
\n\n$ git show-ref --heads\nbf62196b5e363d73353a9dcf094c59595f3153b7 refs\/heads\/core-tutorial\ndb768d5504c1bb46f63ee9d6e1772bd047e05bf9 refs\/heads\/maint\na07157ac624b2524a059a3414e99f6f44bebc1e7 refs\/heads\/master\n24<\/span>dbc180ea14dc1aebe09f14c8ecf32010690627 refs\/heads\/tutorial-2<\/span>\n1e87486<\/span>ae06626c2f31eaa63d26fc0fd646c8af2 refs\/heads\/tutorial-fixes\nWe can get just the branch-head names, and<\/span> remove \"master\"<\/span>, with the help of the standard utilities cut and<\/span> grep:\n\n\n$ git show-ref --heads | cut -d' '<\/span> -f2 | grep -v '^refs\/heads\/master'<\/span>\nrefs\/heads\/core-tutorial\nrefs\/heads\/maint\nrefs\/heads\/tutorial-2<\/span>\nrefs\/heads\/tutorial-fixes\nAnd<\/span> then we can ask to see all the commits reachable from master but not from these other heads:\n\n\n$ gitk master --not $( git show-ref --heads | cut -d' '<\/span> -f2 |\n                grep -v '^refs\/heads\/master'<\/span> )\nObviously, endless variations are possible; for<\/span> example, to see all commits reachable from some head but not from any tag in the repository:\n\n\n$ gitk $( git show-ref --heads ) --not  $( git show-ref --tags )\n(See git rev-parse for<\/span> explanations of commit-selecting syntax such as<\/span> --not.)<\/code><\/span>Code language:<\/span> PHP<\/span> (<\/span>php<\/span>)<\/span><\/small><\/pre>","protected":false},"excerpt":{"rendered":"
Branches, remote-tracking branches, and tags are all references to commits. All references are named with a slash-separated path name starting with “refs”; the names we’ve been using so far are actually shorthand: 1 2 3 – The branch “test” is short for “refs\/heads\/test”. – The tag “v2.6.18” is short for “refs\/tags\/v2.6.18”. – “origin\/master” is short…<\/p>\n","protected":false},"author":1,"featured_media":0,"comment_status":"open","ping_status":"closed","sticky":false,"template":"","format":"standard","meta":{"_kad_post_transparent":"","_kad_post_title":"","_kad_post_layout":"","_kad_post_sidebar_id":"","_kad_post_content_style":"","_kad_post_vertical_padding":"","_kad_post_feature":"","_kad_post_feature_position":"","_kad_post_header":false,"_kad_post_footer":false,"_kad_post_classname":"","_joinchat":[],"footnotes":""},"categories":[2],"tags":[],"class_list":["post-30839","post","type-post","status-publish","format-standard","hentry","category-uncategorised"],"_links":{"self":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/30839","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/comments?post=30839"}],"version-history":[{"count":1,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/30839\/revisions"}],"predecessor-version":[{"id":30840,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/posts\/30839\/revisions\/30840"}],"wp:attachment":[{"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/media?parent=30839"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/categories?post=30839"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/www.devopsschool.com\/blog\/wp-json\/wp\/v2\/tags?post=30839"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}