Introduction

Git does not store a permanent "parent branch" field for a branch. What you can usually find is either the branch's current upstream or, if you need the historical fork point, the commit history that most likely shows where the branch diverged from another branch.

Check the Current Upstream First

If your branch tracks a remote branch, that is the easiest and most explicit answer Git can give you.

git branch -vv

The current branch line often includes something like:

* feature-x 1234abc [origin/main] Add new endpoint

That means the current branch is configured to track origin/main.

For a machine-readable form, use:

git rev-parse --abbrev-ref --symbolic-full-name @{upstream}

If an upstream exists, this prints something like:

origin/main

Upstream Is Not the Same as Original Base

This is the most important distinction. A branch may:

• have been created from origin/main
• later be rebased onto origin/release
• currently track origin/develop

Git stores the current upstream configuration, but it does not record a permanent label saying "this branch was born from branch X."

So there are really two questions:

• what does the branch track now
• where did it likely fork from originally

Use merge-base to Infer the Likely Fork Point

If you want to compare your branch with likely candidate branches, git merge-base is the standard tool.

git merge-base HEAD origin/main
git merge-base HEAD origin/develop
git merge-base HEAD origin/release

Each command returns the best common ancestor commit between your current branch and the candidate branch. The branch whose merge base best matches the divergence point you expect is often the likely source branch.

You can then inspect the divergence with:

git log --oneline --left-right origin/main...HEAD

If there are only a few commits on the right side beyond origin/main, that is often a strong hint that main was the base.

Reflog Can Help If the Branch Was Created Recently

If the branch was created not too long ago and the reflog entry still exists, Git may show the creation action directly.

git reflog show --date=iso my-branch

If you created the branch with a command such as:

git switch -c my-branch origin/main

then the reflog may preserve enough history to recover that fact more directly than guesswork with merge bases.

Inspect Branch Configuration Explicitly

The current tracking configuration is stored in Git config:

git config --get branch.$(git branch --show-current).remote
git config --get branch.$(git branch --show-current).merge

Typical output:

origin
refs/heads/main

Together, those settings tell you the remote and remote branch the local branch is configured to track.

Common Pitfalls

The biggest pitfall is assuming the upstream branch must be the original parent branch. It often is, but Git does not guarantee that.

Another common mistake is trying to recover a branch name from commit ancestry alone. Commits know their parent commits, but Git does not attach branch-name intent to each commit.

Developers also forget that rebases and changed tracking configuration can make the branch's current relationship look different from its original creation point.

Summary

• Git does not store a permanent parent-branch field.
• Use @{upstream} or git branch -vv to find the branch's current remote tracking branch.
• Use merge-base and history comparison to infer the likely original base.
• Reflog can help if the branch was created recently.
• Treat "current upstream" and "original base branch" as different questions.