Repository navigation
GitHawk 0.3.0
Still marked Preview on the Marketplace: the known limitations at the bottom
of the README are real, and a 1.0 should not have them. Everything below shipped
to the pre-release channel first, as 0.2.48 through 0.2.60.
Added
-
The panel follows your VS Code theme. Every colour in the webview now
comes from VS Code's own tokens — surfaces from the editor, side bar and panel
backgrounds, text fromforegroundanddescriptionForeground, the primary
button from the button tokens, row hover and selection from the list tokens.
On a light theme GitHawk is light; on a high-contrast theme it is
high-contrast. It was previously dark whatever you had chosen, which is the
limitation the README led with.Lane colours stay fixed. They are identity rather than chrome — a lane has to
keep its colour as your eye follows it down the graph, and stay distinct from
the seven beside it — so they are eight mid-saturation hues chosen to hold
their contrast against white and near-black alike.Warnings deliberately do not use
charts-orange: it is
rgba(234, 92, 0, 0.33)in both default themes, a highlight fill rather than
a foreground, and text drawn in it is nearly invisible on white. They use
editorWarning-foreground, which is what the editor uses to say the same
thing. -
The graph reloads by itself when the repository changes. A commit, checkout,
fetch, rebase, or stash made in a terminal, in VS Code's own Source Control
view, or by a tool running in a worktree now reaches the panel without pressing
Refresh. GitHawk watches git's metadata —HEAD,refs,packed-refs, the
index, and the in-progress operation markers — in both the per-worktree and the
shared git directory, so a commit made in another worktree of the same
repository counts too. Writes are coalesced, so one rebase is one reload rather
than one per replayed commit. Turn it off withgitHawk.autoRefresh. -
"Show changes in the sidebar" on the commit menu, first under Compare.
Selecting a commit has always filled the Changes tree, but the view is only
surfaced once — after that there was no way to ask for it back without
selecting a different commit and returning. -
A reload keeps your place: the row at the top of the viewport stays there
rather than sliding down as new commits arrive above it, and a selected commit
that no longer exists after an amend or a rebase is dropped rather than left
describing history that has gone. -
Push and pull one named branch, from its own menu. A new Sync group,
first, offering both every time rather than only when there is something to do
— the state goes in the description (3 behind,nothing to push,already up to date). A branch that tracks nothing offers Publish, which sets the
upstream so later pushes need no arguments, and asks which remote when there is
more than one. Pulling a branch that is not checked out still writes the ref
directly rather than touching the working tree; pulling the current branch is a
pull, because git refuses a refspec fetch into it. No--forceanywhere. -
A Remotes button on the toolbar, beside Fetch, Pull, and Push. Managing
remotes was reachable only from the command palette, which is a poor place for
it when its three neighbours are buttons. -
GitHawk: Manage Remotes— add, rename, re-point, or remove a remote, fetch
one with pruning, or prune deleted branches without fetching. Fetch and push
URLs are listed separately when they differ, as a fork checkout's do. Removing
a remote and pruning are confirmed first: both delete tracking refs that the
reflog cannot restore. -
"Copy branch name" on the branch menu, for local, remote, and the
checked-out branch. A commit could always copy its hash; a branch name — the
one people retype into a checkout, a PR description, or a CI filter — could
not be copied at all, and a webview cannot be text-selected. -
Branch labels on the graph are click targets, opening the same menu the
branch list does. Tags and a detached HEAD stay inert, because neither has a
branch menu to open.
Changed
-
The branch menu's Update group is now Sync, and holds push and pull
alongside the diverged andgonewarnings that were already there. The
fast-forward entry for a branch you are not standing on is now worded as a pull,
since that is what it is asked to do; it still moves only the ref. -
Clicking a branch label on a commit row opens that branch's menu rather than
selecting the commit. Clicking anywhere else on the row still selects it. -
Uncommitted work has a row in the graph. Above the newest commit whenever
there is anything to show, with what kind —2 staged, 1 modified, 3 untracked— and gone again when the tree is clean. Selecting it fills the
Changes tree with everything uncommitted as one changeset againstHEAD, the
same comparisonGitHawk: Show Uncommitted Changesruns. Its marker is hollow
and dashed rather than a commit dot, and nothing draws a line from it to
HEAD: the graph reads every ref, so the topmost row is frequently not the
commit the changes sit on.Selecting the row brings the Changes view to the front every time, unlike
selecting a commit, which surfaces it once and then leaves it alone. There is
only one working-tree row and nothing to browse through, so clicking it is
only ever a request to see the files.Untracked files are counted in the row but are not in the changeset —
git diff HEADhas no blob to compare a file git has never seen against. The row's
tooltip says so. -
The branch list and the commit details pane fold away. The graph lives in
the bottom panel, which is short and splits its width three ways, so the thing
the panel exists to draw had the least room of the three. A thin handle on
either side of the graph toggles its pane, and stays put when the pane is gone
— the way back is where the way out was. The choice is remembered across the
panel being hidden, rebuilt, and the window reloaded.