How to View an All-Branches Graph in Bitbucket

To see all branches in a Bitbucket commit graph, open the repository’s Commits view and choose Show all when you use Stiltsoft Commit Graph; Bitbucket Data Center’s native graph must also be enabled on the instance. An all-branches graph helps you trace where work diverged, merged, or was abandoned without opening every branch separately.

The instructions focus on Bitbucket Data Center and the Commit Graph interface documented for it. Bitbucket Cloud and customized Data Center installations can present different navigation or graph options.

What an All-Branches Graph Shows

A commit graph is a visual representation of Git ancestry:

  • A line, or lane, connects a commit to its parent commit.
  • A split shows where development diverged into separate lines of work.
  • A merge commit joins lines back together.
  • A branch name is a reference pointing to a commit; it is not a separate copy of every earlier commit.

That distinction matters when reading an all-branches view. If main and feature/login both contain the same older commits, those shared commits appear once in the graph. The graph shows their relationship, while branch labels identify the references that point into that history.

An all-branches graph is best for understanding repository topology. It is not the best tool for answering, “What files would change if I merge this branch?” Use Bitbucket’s comparison view for that question.

Choose the Right Bitbucket View

Use the combined commit history to understand topology, and use Compare when you need the actual difference between two chosen revisions.

The table maps common repository questions to the Bitbucket view or local Git command that answers each one.

Your goal Best view or command What it gives you
See development across branches Commits with Show all A combined graph and commit list
Follow one branch or tag Commits branch/tag drop-down A graph scoped to that reference
See what a feature branch changes Compare with Source and Destination Diff and commit list between selected refs
Compare refs from separate forks Compare Branches, tags, or commits from different forks
Inspect the files in one commit Local Git ls-tree The file paths stored by that commit
Get an all-refs graph when the web UI is unavailable Local Git log --graph --all An ASCII graph of local and remote-tracking refs

How to View an All-Branches Graph in Bitbucket

Bitbucket’s Commits page can display commits across branches in the graph when you select Show all.

Step 1: Open the Repository Commits View

  1. Open the Bitbucket repository.
  2. In the repository sidebar, select Commits.
  3. Look at the area immediately left of the Author column for the graph lanes.

In Stiltsoft’s Commit Graph documentation, this is where its Commit Graph appears for the current repository. If you see a normal commit list but no lanes, the graph feature may not be enabled on the server.

Stiltsoft Commit Graph version 5.10.0 disables its add-on graph in favor of Bitbucket’s standard graph. For that standard graph to appear, a Bitbucket administrator can set feature.commit.graph to true in bitbucket.properties and restart the Bitbucket instance.

Step 2: Switch the Commit List to All Branches

  1. Stay on the Commits page.
  2. Find the Show all link.
  3. Select it to display commits across branches in the graph.

For Stiltsoft Commit Graph, Show all is the control that changes the current reference view into an all-branches view.

A branch graph can become visually busy in repositories with many old branches. Start by locating the current integration branch, then trace outward at merge commits or branch labels rather than trying to read every lane from top to bottom.

Step 3: Scope the Graph to One Branch or Tag When Needed

An all-branches view is useful for orientation, but a narrower view is often easier to inspect.

  1. Open the branch or tag drop-down on the Commits page.
  2. Select a branch or tag.
  3. Review the updated commit list and graph for that selected reference.

Stiltsoft’s Commit Graph scopes both the displayed graph and commits when you select a branch or tag from that drop-down. This is useful when you want to follow one release tag, verify a short-lived feature branch, or reduce graph noise before reviewing history.

Step 4: Highlight a Commit’s Ancestors

Clicking a point in Stiltsoft Commit Graph highlights the ancestors of that changeset. This can make it much easier to answer questions such as:

  • Which branch did this commit originate from?
  • Was this commit merged through an intermediate branch?
  • Which commits lead into this merge commit?

To clear the selection and restore highlighting for all changesets, click anywhere in the graph outside the commit points.

Compare Two Branches or Commits in Bitbucket

Use Compare when you need a revision difference rather than a history map. Bitbucket Data Center provides the Compare page from version 6.3 onward.

  1. Open the repository sidebar and choose Compare.
  2. In the Source drop-down, choose the branch, tag, or commit you want to compare from.
  3. In the Destination drop-down, choose the target branch, tag, or commit.
  4. Review both the diff and the commits list tabs.

Atlassian’s Bitbucket Data Center documentation states that Source and Destination can be any combination of branches, tags, and commits. They can also come from different forks when those forks are available to you.

For a feature branch compared with its destination branch, a three-dot diff focuses on work since the feature branch was last synchronized with the destination. A two-dot diff directly compares the two selected commit references. That difference explains why a comparison can show fewer or more changes than you expect when the branches have been rebased, merged, or synchronized at different points.

Use the three-dot style when reviewing the feature work introduced relative to its shared history. Use the two-dot style when you need the literal file difference between two exact commits or refs.

View a Commit Tree or All Refs Locally

The Bitbucket web graph is convenient, but Git gives you a reliable fallback when the graph is disabled, the Commits option is unavailable, or you need to inspect an exact commit object.

List the Files Stored in a Commit

From a clone of the repository, run this command and replace <commit> with a commit SHA, tag, or branch name:

This lists the file paths contained in that commit. The slash-separated paths show the directory structure, which is often more useful than a changed-files diff when you need to know what the repository looked like at a specific revision.

A commit’s changed-files view answers “what changed from its parent?” A tree listing answers “what files exist in this commit?” Those are different questions, especially for merge commits and commits that make no file changes.

Render an All-Branches Graph in the Terminal

Run this from the repository directory:

git log --graph --decorate --oneline --all

--graph draws the ancestry lanes, --decorate adds branch and tag names when available, --oneline keeps each commit compact, and --all includes all refs Git knows about. This includes local branches, tags, and remote-tracking branches in your clone.

I use Git for this fallback because the terminal graph makes the exact refs and commit IDs visible without depending on a server-side UI feature.

Remember that a local graph only knows the refs your clone has fetched. If another developer pushed a branch after your last fetch, it will not appear locally until your remote-tracking refs are updated.

Fix Missing or Confusing Commit Graphs

The Commits Page Is Visible but Has No Graph Lanes

First, verify that you are looking at a repository page rather than a project overview or pull-request-specific commit list. The graph documented by Stiltsoft appears on the repository’s Commits page, to the left of the Author column.

On installations using Bitbucket’s standard graph, an administrator may need to set feature.commit.graph to true in bitbucket.properties and restart the instance. Stiltsoft Commit Graph 5.10.0 relies on that standard graph instead of rendering its former add-on graph.

If you do not administer the instance, provide the administrator with the repository URL, a screenshot of the Commits page, and the Bitbucket Data Center version. Meanwhile, use the local git log --graph --decorate --oneline --all command to inspect the repository history.

The Show All Control Is Missing

Try the branch or tag selector first. If it only lets you scope to one ref and provides no all-branches option, use the local Git graph command. It produces the same underlying Git ancestry view from the refs available in your clone.

Commit Dates Look Out of Order

A Git graph follows parent-child relationships, not a simple chronological timeline. A commit can have an author date that differs from its committer date, and operations such as rebasing and cherry-picking can create newer commits that contain older authored changes.

Do not diagnose branch ancestry from dates alone. Follow the graph lanes, inspect merge commits, and compare commit IDs. If you need the exact author and committer timestamps for a commit, run:

git show --no-patch --format=fuller "<commit>"

Confirm the Graph Answers Your Question

Before acting on what you see, check that the view matches the question you were trying to answer:

  • The all-branches graph contains the branch tips or tags you expected to inspect.
  • A selected branch or tag view contains the expected commits for that ref.
  • A merge commit connects the expected lines of history.
  • The Compare page shows the intended Source and Destination refs.
  • The comparison’s commits list and file diff match your intended review scope.
  • A local terminal graph includes the remote-tracking branches you expect your clone to know about.

If the graph suggests a branch was merged but the comparison still shows changes, compare exact commit IDs rather than branch names. Branch names can move, while a commit SHA identifies one immutable commit object.

Frequently Asked Questions

How do I view a commit graph in Bitbucket?

Open the repository sidebar’s Commits page and look for graph lanes left of the Author column. In Stiltsoft Commit Graph, select Show all to combine branch history, or use the branch/tag drop-down to narrow the graph to one reference. If no graph lanes appear, the Bitbucket Data Center instance may need its standard commit graph enabled.

Is There a Network View for Bitbucket?

An all-branches commit graph is the closest practical equivalent to a network view for repository history. It shows branch divergence, merges, and shared ancestors in a compact vertical layout. Use Compare instead when you need a file-level difference between two specific refs.

How Do I Show Only the Changes on a Branch?

Open Compare, select the feature branch in Source, and select its target branch in Destination. Bitbucket Data Center supports this Compare workflow from version 6.3 onward and displays both a diff and a commits list. A three-dot comparison is generally the useful choice for reviewing work introduced on a feature branch since its shared synchronization point.

How Do I View the File Tree for a Specific Commit?

Use Git locally with a commit SHA, branch name, or tag:

git ls-tree -r --name-only <commit>

The command lists every file path stored in that commit. This differs from a Bitbucket commit diff, which only shows files changed relative to a parent commit.

Why Does the Bitbucket Graph Look Wrong When Commit Dates Are Out of Order?

Commit dates do not define Git ancestry. Rebases, cherry-picks, amended commits, and different author-versus-committer timestamps can make chronological ordering look surprising while the parent relationships remain valid. Follow the lane connections and commit IDs, then use Compare if you need to verify the actual content difference.

Open the repository’s Commits view first to understand the overall history, then switch to Compare before making a merge or release decision.