← Commitlane for VS Code

Commitlane support

Find your symptom below. If it isn't here, email support@voussoirsoftware.com and a person will answer.

Getting started

Opening the graph

Open the command palette and run Commitlane: Open Git Graph, or click the branch icon at the top of the Source Control panel. Your open folder has to sit inside a git repository.

Moving around

• Click a row to select it.
• Double-click to open that commit's diff beside the graph.
• Cmd-C or Ctrl-C copies the selected commit's full hash.
• Search matches the message, author or hash. Enter jumps to the next match, Shift-Enter to the previous, Escape clears it.
• All branches switches between just your current branch and everything in the repo.

Licences

Entering a key

Command palette → Commitlane: Enter Licence Key, then paste it in. You can also set commitlane.licenseKey in your settings, which is easier if you sync settings across machines with a dotfiles repo.

Using it on another machine

Paste the same key. Your licence belongs to you, not to a computer, and there's no activation count to burn through. The check runs locally, so it works with no network at all.

"That licence key is not valid"

Nearly always a copy that dropped a character. Your key is one unbroken string starting CL1., with two full stops in it and no spaces or line breaks. Mail clients sometimes wrap it across lines. Copy it again from the original email, or ask us and we'll send a fresh one.

The trial ended and I had not finished deciding

Email support@voussoirsoftware.com and we'll extend it. We'd rather you made up your mind properly than bought something you weren't sure about.

When the graph looks wrong

The graph is very wide

On a heavily branched repo, it is. Git's own source sprawls dozens of lanes across, and git log --graph draws it exactly the same way. Past a couple of dozen we stop drawing lines so the commit messages stay readable, and a note appears in the bottom right while that's happening. Switching all branches off narrows things a lot.

Nothing appears, or it says there is no repository

Your open folder has to be inside a git repository, and git has to be on the PATH VS Code sees. On macOS that often isn't the same PATH your shell has. Run git --version in VS Code's integrated terminal to check.

The history looks out of order

Commitlane draws commits in topological order rather than by date, exactly as git log --graph does. Ordering by date tangles together every branch that was active at the time and the graph turns to spaghetti. So yes, a newer date can appear below an older one.

A very large repository takes a moment on first open

Your first search builds an index of the repo, which takes a moment on something really large, and every search after that reuses it. Opening the graph itself doesn't wait for any of this.

Privacy

Commitlane makes no network requests at all. It runs your git against your checkout and draws what comes back. No account, no sign-in, no telemetry, and your licence gets checked offline. The privacy page spells it out.