{"id":3056,"date":"2026-02-16T14:34:42","date_gmt":"2026-02-16T14:34:42","guid":{"rendered":"http:\/\/www.nikola-breznjak.com\/blog\/?p=3056"},"modified":"2026-02-16T14:36:36","modified_gmt":"2026-02-16T14:36:36","slug":"how-to-find-a-branch-parent-git","status":"publish","type":"post","link":"https:\/\/nikola-breznjak.com\/blog\/miscellaneou\/how-to-find-a-branch-parent-git\/","title":{"rendered":"How to find a branch parent in Git"},"content":{"rendered":"

You know that moment when you’re staring at a branch named feature\/whatever<\/code> and thinking:<\/p>\n

\n

"Cool\u2026 but what was this branched off from?"<\/p>\n<\/blockquote>\n

Maybe you’re cleaning up old branches, reviewing a PR, or trying to figure out why feature\/foo<\/code> contains commits from three different universes. Either way: Git doesn’t explicitly store "parent branch" metadata (because branches are just pointers to commits). But we can<\/em> usually infer it.<\/p>\n

In this post, we’ll use a practical one-liner that prints the most likely parent branch of your current branch.<\/p>\n

What we’re building<\/h2>\n

A small command that you can run on any branch to get a best-guess "parent branch" name.<\/p>\n

Here’s the solution:<\/p>\n

git show-branch | sed "s\/].*\/\/" | grep "\\*" | grep -v "$(git rev-parse --abbrev-ref HEAD)" | head -n1 | sed "s\/^.*\\[\/\/"<\/code><\/pre>\n
If you like, you can wrap it in a function later so it’s easier to run. But first, let’s understand what’s going on.<\/p>\n
The command (run it on the branch you’re investigating)<\/h2>\n
Step 1: checkout the branch:<\/p>\n
git checkout feature\/my-branch<\/code><\/pre>\n
Step 2: run the one-liner:<\/p>\n
git show-branch | sed "s\/].*\/\/" | grep "\\*" | grep -v "$(git rev-parse --abbrev-ref HEAD)" | head -n1 | sed "s\/^.*\\[\/\/"<\/code><\/pre>\n
What you’ll get back<\/h3>\n
Something like:<\/p>\n
main<\/code><\/pre>\n
Meaning: "Given what I see in the commit graph, main<\/code> looks like the most likely branch this one came from."<\/p>\n
And voil\u00e0, your repo just got a little less mysterious.<\/p>\n
How it works (without turning this into a PhD)<\/h2>\n
This is a pipeline. Each part trims the output until we’re left with a single branch name.<\/p>\n
1) git show-branch<\/code><\/h3>\n
This command prints a compact view of commits and the branches they belong to. It’s useful when you want to compare branches and see where they intersect.<\/p>\n
The raw output is noisy, but it includes bracketed branch names like:<\/p>\n
* [main] ...\n ! [feature\/my-branch] ...<\/code><\/pre>\n
2) sed "s\/].*\/\/"<\/code><\/h3>\n
This removes everything after the ]<\/code>, leaving just:<\/p>\n
* [main\n ! [feature\/my-branch<\/code><\/pre>\n
We’re basically stripping commit messages and keeping only the branch label portion.<\/p>\n
3) grep "\\*"<\/code><\/h3>\n
This keeps only lines containing *<\/code>.<\/p>\n
In git show-branch<\/code> output, *<\/code> is used to highlight a particular row of interest across branches (in practice, it helps narrow candidates to "closest" related branches).<\/p>\n
4) grep -v "$(git rev-parse --abbrev-ref HEAD)"<\/code><\/h3>\n
Now we remove the current branch name from the list.<\/p>\n
Because if Git returns your branch as its own parent, that’s not helpful (and slightly insulting).<\/p>\n
git rev-parse --abbrev-ref HEAD<\/code> prints the current branch name, so this part is a clean "exclude me".<\/p>\n
5) head -n1<\/code><\/h3>\n
We take the first remaining match\u2014basically the best candidate from the top.<\/p>\n
This is one reason I call the output a "best guess". It’s a very useful guess, but it’s still based on how git show-branch<\/code> orders things.<\/p>\n
6) sed "s\/^.*\\[\/\/"<\/code><\/h3>\n
Finally, remove everything up to the [<\/code>, so we’re left with just:<\/p>\n
main<\/code><\/pre>\n
Quick recap \u2705<\/h2>\n
At this point, you have a one-liner that prints the most likely parent branch, a quick way to sanity-check where a feature branch probably started, and a decent understanding of the pipe magic so it doesn’t feel like copy-paste sorcery.<\/p>\n
Make it easier to use (optional but recommended)<\/h2>\n
If you find yourself using this often, add a helper function to your shell config (~\/.zshrc<\/code> or ~\/.bashrc<\/code>):<\/p>\n
git-parent() {\n  git show-branch \\\n    | sed "s\/].*\/\/" \\\n    | grep "\\*" \\\n    | grep -v "$(git rev-parse --abbrev-ref HEAD)" \\\n    | head -n1 \\\n    | sed "s\/^.*\\[\/\/"\n}<\/code><\/pre>\n
Now you can just run:<\/p>\n
git-parent<\/code><\/pre>\n
Much nicer.<\/p>\n
Caveats (because Git is Git)<\/h2>\n
This works best when your repo follows a normal branching model (feature branches off main<\/code>\/master<\/code>\/develop<\/code>), when you have the relevant branches locally (run git fetch --all<\/code> if needed), and when your history hasn’t been heavily rewritten in weird ways.<\/p>\n
Things that can confuse "parent branch" inference: rebasing after branching, lots of cherry-picks from multiple branches, branching off a feature branch and then merging from other places, or when the real parent branch was deleted.<\/p>\n
So treat the output as: "most likely parent branch"<\/strong>, not a guaranteed truth.<\/p>\n
Want to read more?<\/h2>\n
If you want to go beyond "best guess" and explore exact branch points, merge-bases, fork-points, and different strategies, these two Stack Overflow threads are gold:<\/p>\n
http:\/\/stackoverflow.com\/questions\/1527234\/finding-a-branch-point-with-git<\/a><\/p>\n
http:\/\/stackoverflow.com\/questions\/3161204\/find-the-parent-branch-of-a-git-branch<\/a><\/p>\n
Final thoughts<\/h2>\n
Git doesn’t store a "parent branch", but with the commit graph and a bit of filtering, you can usually infer it quickly:<\/p>\n
git show-branch | sed "s\/].*\/\/" | grep "\\*" | grep -v "$(git rev-parse --abbrev-ref HEAD)" | head -n1 | sed "s\/^.*\\[\/\/"<\/code><\/pre>\n
Next time someone asks "where did this branch come from?", you’ll have an answer\u2014and you won’t even need to blame your coworker. \ud83d\ude09<\/p>\n","protected":false},"excerpt":{"rendered":"
You know that moment when you’re staring at a branch named feature\/whatever and thinking: "Cool\u2026 but what was this branched off from?" Maybe you’re cleaning up old branches,…<\/p>\n","protected":false},"author":1,"featured_media":4790,"comment_status":"open","ping_status":"open","sticky":false,"template":"","format":"standard","meta":{"footnotes":""},"categories":[32],"tags":[],"class_list":["post-3056","post","type-post","status-publish","format-standard","has-post-thumbnail","hentry","category-miscellaneou"],"_links":{"self":[{"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/posts\/3056","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/posts"}],"about":[{"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/types\/post"}],"author":[{"embeddable":true,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/users\/1"}],"replies":[{"embeddable":true,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/comments?post=3056"}],"version-history":[{"count":2,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/posts\/3056\/revisions"}],"predecessor-version":[{"id":3058,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/posts\/3056\/revisions\/3058"}],"wp:featuredmedia":[{"embeddable":true,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/media\/4790"}],"wp:attachment":[{"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/media?parent=3056"}],"wp:term":[{"taxonomy":"category","embeddable":true,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/categories?post=3056"},{"taxonomy":"post_tag","embeddable":true,"href":"https:\/\/nikola-breznjak.com\/blog\/wp-json\/wp\/v2\/tags?post=3056"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}