Skip to the content.

GitHub Tree Navigator Usage Guide

GitHub Tree Navigator adds a collapsible file-tree sidebar to GitHub repository and pull request pages. This guide covers the fastest way to get comfortable with the extension and explains the features that are easiest to miss.


Getting Started

  1. Install the extension from the Chrome Web Store or load the unpacked dist/ folder in chrome://extensions.
  2. Open any repository on github.com.
  3. Move to the left edge of the page and open the sidebar.
  4. Start typing in the search field to filter the tree immediately.
  5. Click a file to open it in GitHub without losing the tree context.

If the sidebar is pinned, it stays visible while you navigate. If it is not pinned, it can auto-hide when your cursor leaves the sidebar area.


Core Navigation

Browse the repository tree

Search files quickly

Use quick file actions

Each file row includes lightweight actions for common tasks:

These actions are useful when reviewing code, sharing links, or jumping into Git history quickly.


Pull Request Mode

On pull request pages, the sidebar switches from the full repository tree to a tree of changed files in that pull request.

Use this mode when you want to:

If you review pull requests often, this is one of the highest-value features in the extension.


Pinning and Resizing

Pin mode

Resizing

The extension also applies the saved width before first paint on pinned reloads to avoid visible layout shift.


Private Repositories and Rate Limits

By default, GitHub API requests are unauthenticated. That works for public repositories, but the rate limit is lower.

If you need more API capacity or access to private repositories:

  1. Open the extension settings.
  2. Add a GitHub Personal Access Token.
  3. Use repo scope for private repositories, or public_repo for public-only access.

The token is stored in chrome.storage.local in your browser and is only used for GitHub API requests.


Large Repositories

Some very large repositories cause GitHub’s recursive Trees API response to be truncated.

When that happens, GitHub Tree Navigator automatically falls back to lazy directory loading instead of failing silently.

In fallback mode:

This tradeoff keeps the extension usable on repositories that would otherwise be too large for a single tree response.


Keyboard Shortcuts


Troubleshooting

The sidebar does not appear

Private repositories do not load

Search shows incomplete results in a huge repository