Repository navigation
Releases
GitHawk 0.8.0
Added
- Browse the whole project at a commit. Right-click a commit and choose
Browse files at this commit: every file the project had at that point —
not only the ones the commit changed — fills a Files tree in the sidebar,
beside Changes, laid out like the Explorer with folder counts and your
file icon theme. A file opens that commit's version of itself, read-only,
through the same revision scheme the diff editor already uses, so syntax
highlighting, blame, and Reveal In Explorer View all work on it. Hover a
row for Compare With Working Tree. Nothing is checked out and the working
tree is untouched. The view appears when a commit is browsed and leaves with
the × in its title bar;GitHawk: Browse Files At A Commitreaches it
from the palette and asks which branch, tag, or commit.
GitHawk 0.7.0
The release that closes the loop. Until now GitHawk showed you what you had
not committed and left the committing to someone else; the Changes view is now
where a commit is put together — staged and unstaged in git's own sections,
untracked files at last in the list, a message box above them, and an AI CLI
of your choice a click away to write the message. Still no model inside
GitHawk: the tool is yours, run once, through your own shell.
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.
Added
-
Commit from the Changes view. The uncommitted-changes row now fills the
sidebar with the working tree in git's own sections — Staged Changes,
Changes, Untracked Files, and Merge Conflicts when there are any —
and puts a Commit box above them. Hover a row for + and − to stage
and unstage; on a section or a folder they take everything beneath. Each row
opens the diff its section means:HEADagainst the index for a staged file,
the index against the disk for an unstaged one.The button says what it will do —
Commit 2 staged files, orCommit all changeswhen nothing is staged, which asks before staging everything.
⌘/Ctrl Enter presses it. The draft survives
clicking around the graph, and the box leaves with the last uncommitted file. -
Generate the message with an AI CLI. A select beside the box names the
tools fromgitHawk.aiToolsthat have acommitMessageCommand— Claude Code,
Codex, Gemini CLI and opencode out of the box — and Generate pipes the
diff of what would be committed to the chosen one, once, non-interactively,
through your shell. What it prints lands in the box for you to edit; nothing
is committed on the strength of it, and nothing runs inside GitHawk. -
Untracked files are in the changeset. They were counted in the row and
absent from the tree, becausegit diff HEADhas no blob for a file git has
never seen. The working tree is now read in sections, and the untracked one
comes fromls-files --others, so the row and the tree finally agree. -
The tree keeps up with the working tree. Saving a file, or creating,
deleting or renaming one through the explorer, moves it to the section it now
belongs in, without pressing Refresh. The graph's watcher still ignores the
working tree on purpose; this is a cheaper read of just the uncommitted side. -
Reveal in Explorer View, from a diff. Every diff GitHawk opens has the
button in its title bar and its tab's right-click menu. VS Code's own reveal
works on a file on disk and not on the historical side of a diff, which has
a path and no location until it is joined to its repository; this does both.
The Changes tree's rows offer it on right-click too.Cmd+K Xruns it from
the editor, and it joins the GitHawk submenu of the editor's right-click
menu, where the chord is printed beside it. -
Cmd+Shift+9opens the Changes sidebar with the keyboard on the tree —
the graph panel'sCmd+9, with Shift. -
Cmd+9again hides the panel. With the graph focused, the key that
opened it closes the whole bottom panel, so one key summons and dismisses
it. From anywhere else it still opens and focuses the graph. The page
claims the key itself: the workbench'sfocusedViewcontext is not set
while focus is inside a webview, so a keybinding on it never fires. -
Expand all, beside collapse all. VS Code gives a tree the one and not
the other; the Changes view's title bar now has both. -
Commands:
GitHawk: Commit,GitHawk: Stage All Changes,GitHawk: Reveal In Explorer View,GitHawk: Open Changes Sidebar, andGitHawk: Write The Commit Message With An AI CLI. The Changes view's title bar gained
a button for the uncommitted changes.
Fixed
- The arrows reach the uncommitted-changes row. ↑ on the newest
commit stopped dead with the row visibly above it. It is a row now: Up lands
on it, Home jumps to it, Enter is its click, and Down comes back to the graph.
GitHawk 0.6.0
The release that makes the mouse optional. Hold Shift and the panel tells you
every key it has; the graph takes a cursor and the arrows move it; three chords
reach git from the editor.
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.
Added
-
Hold Shift to see the keyboard. Every control that has a shortcut shows
its key on the control itself while Shift is held; keep holding and press the
key to run it. Basecamp's idea, and it works because the list of shortcuts is
the screen rather than a page in the documentation — always accurate, always
beside the thing it acts on.A badge appears only where the key does something, and the same list decides
both, so the two can never disagree: fold the branch list away and its four
keys leave with its badges.Refresh, fetch, pull and push are
R F U P; the repository picker isO; the
two side panes areBandD; the branch filter isK; the three managers
areM,WandS; a multi-commit selection addsCandX. -
Check out a branch from the toolbar, or with
Shift+T. The branch name
beside the repository was a label; it is a picker now, for the same reason the
repository next to it is one. Switching branch was the most common thing a git
tool does and the only one that needed the sidebar, a filter, three tabs and a
menu to reach. -
Three keys in the editor, all chords under
Cmd/Ctrl+K, none of them
bound by VS Code already:Cmd+K BBlame on, and off again Cmd+K HWho wrote this line Cmd+K GShow this line's commit in the graph All three are in the editor's right-click menu too, under a GitHawk
submenu, which is where they announce themselves: VS Code prints each item's
chord beside it, and a shortcut nobody can find is a shortcut nobody has. The
hover card namesCmd+K Gnext to its "show in the graph" link for the same
reason.Cmd+K Hshows the card the mouse already gets, at the caret, and works
whether or not the annotations are on — turning the column on to ask one
question and off again afterwards is the work it saves.The card moved from the decorations to a real hover provider to get there:
only a provider's contribution can be opened from the keyboard. That also
fixed it being drawn twice, once from each source, and means a hover anywhere
on the line answers rather than only one over the label.
Fixed
-
"Show in the graph" no longer errors when the file is in another
repository. A workspace usually holds several, and the file being read is
often not in the one the panel is pointed at. The commit was looked up in the
wrong repository and the answer wasGitHawk could not compare: fatal: bad object— nothing was missing and nothing was wrong, the question had simply
gone to the wrong place. GitHawk now follows the file: it switches to the
repository the line belongs to, waits for that graph, and then shows the
commit. -
"Show in the graph" works with the panel closed. Opening the panel does
not build it, so the reveal was sent to a webview that did not exist yet and
dropped: the Changes tree filled, the graph selected nothing, and it read as
the request being ignored. The message now waits for somewhere to send to, and
the graph holds a reveal that names a commit whose rows have not arrived. -
Drive the graph without the mouse.
Shift+Gputs a cursor on a commit;
the arrows,Home,End,PgUpandPgDnmove it;Enteris the left click
andShift+Enterthe right one. The cursor is not the selection, which is
what makes it cheap: reading your way down a branch asks the host nothing,
where a cursor that selected as it moved would spawn a worktree per keystroke.Shift+VturnsSpaceinto a picker, with a banner that says so — a mode
you can be in without knowing is the one thing wrong with modes. Nothing is
sent while you choose, which is the whole point:Enterthen shows the
combined changes and leaves,Escleaves and keeps the picks.Shift+Aasks for the selection's changes at any time, however it was made.Rows are a real listbox now — one roving tab stop rather than five hundred, a
focus ring on the cursor, androle="option"witharia-selected, so a screen
reader is told what a sighted reader can see.The three graph keys act on the whole list rather than on any one control, so
they have nowhere to hang a badge. They get a strip of their own in the corner
of the graph, on the sameShift, with a word each — a bare letter is enough
on a button that already says "Refresh" and says nothing floating over a graph. -
Expand the panel to the window, with the
⇕button in the toolbar or
Shift+E. The panel's height belongs to the workbench, so this asks VS Code
to run its owntoggleMaximizedPanel— which is also why it is one toggle and
not two buttons: there is no way to ask which state the panel is in.VS Code already has a chevron for this in the panel's title bar. Duplicating it
is deliberate: a graph is the one thing in that panel that always wants more
height, the title bar is chrome most readers never look at, and a shortcut has
to have a control to put its badge on.The badges wait a quarter of a second before appearing, because Shift is
already a modifier here — Shift-click extends a selection in the graph — and
without the pause every range made the panel flash a dozen badges. A capital
typed into the branch filter stays a capital, and Ctrl, Cmd and Alt
combinations are left to VS Code.
GitHawk 0.5.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.
Added
-
Each commit's time, beside its date. A date answers "roughly when", which
is enough until someone is reading a day's worth of commits and needs their
order within it. The graph's own order already says which came first; the time
says how far apart.The column pays for it with a two-digit year —
9/4/23, 12:00 PMin place of
9/4/2023— and grows fromw-20tow-32, which costs the subject 48px. A
tooltip carries the full form, weekday and seconds included, for reading a row
without selecting the commit.Both parts follow the host's locale rather than imposing an American one, so
en-GB reads03/09/2023, 18:45. A date column that disagrees with the rest of
the machine is a bug.
Changed
-
The logo is the hawk a designer drew, in the blue colourway —
#CCCCCCto
#4EA3E8, on the near-black plate the same delivery uses — replacing the
hand-drawn eye.The activity bar and the panel take the bird without the crosshair ring: at
24px the ring's arcs are too thin to survive, while the wing and the beak
read. The eye's own comment had predicted a hawk would smudge at that size,
which is true of the full mark and not of the mark cut down for it. -
Every build now reaches Open VSX, not only the stable ones. Open VSX is
where the VS Code forks install from — Cursor, Antigravity, VSCodium,
Windsurf — and the publishing step was gated on the stable channel, so those
users would have sat onX.Y.0while Marketplace users got a build per push
tomain.One
.vsixgoes to both registries rather than one build each, so what a
Cursor user installs is byte-for-byte what a VS Code user does. The step also
no longer skips silently when its token is unset, which was right while the
publisher agreement was pending and wrong now that it is signed: an expired
token would have quietly stopped publishing to half the audience.
Internal
-
The Playwright config pins locale and timezone. Rendering a time in every row
makes the baselines depend on the machine that wrote them —npm run shotsin
Tel Aviv and in London disagree on every row, thousands of pixels of diff
saying nothing about the change under test. Fixture timestamps are UTC, which
is also the zone that keeps their dates off a day boundary. -
ovsxjoinsdevDependenciesalongsidevsce, sonpxresolves it locally
afternpm ci. It was the one unpinned download in the job that holds the
registry tokens.
GitHawk 0.4.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.3.66 through 0.3.74.
Added
-
Blame in the editor.
gitHawk.blame.styleset tocolumngives every line
the date and author of the commit it came from, in a fixed-width column between
the line numbers and the code — IntelliJ's annotate. Each commit has its own
colour and the colours run in order, cool for the oldest lines in the file to
warm for the newest, so a run of lines reads as a block and scrolling shows the
order the file was built in.Ranked by commit rather than scaled by elapsed time, deliberately: a week of
steady work is one shade on a time-proportional scale, and telling one commit
from the next is what the colour is for.Hovering gives the full message, author, date, the number of lines that commit
owns there, and a link that selects the commit in the graph and fills the
Changes tree. Decoration text cannot take a click, so the hover is the way
through.Off by default. Turn it on from the editor's right-click menu, a person icon in
its title bar, orGitHawk: Toggle Blame Annotations— which switches
between off and the column.endOfLineis the quieter placement, one label per
block at the end of its first line, reachable by setting the style directly.Beside the line numbers is not offered: that is the gutter, it takes an image
rather than text, and VS Code scales it to icon size.Annotations appear in the diff editor too, on both sides, each blamed as of its
own revision. And they are read from the editor's buffer rather than the file on
disk, so they stay correct part-way through an unsaved edit instead of shifting
every line below it onto the wrong commit. Redraws are debounced. -
GitHawk: Manage Stashes— the stash, which GitHawk did not touch at all.
Every entry with its message, the branch it was made on and when, marking the
ones git named itself, sinceWIP on main: 1234abc …describes the commit the
work sat on rather than the work. Apply from the list in one click, or open an
entry to show what is in it, apply, pop, or drop.Showing an entry needs no new machinery: a stash is a commit whose first parent
is the commit it was made on, so its contents are that comparison, landing in
the Changes tree like everything else.Stashing asks for a message and whether to include untracked files. Untracked is
never the default and never implied — it is the one variant that sweeps up a
scratch file — and--all, which would take ignored files too, is not offered.
Popping and dropping are confirmed: both remove the entry, and a dropped one
survives only as a dangling commit.Every action re-reads the stack and checks the entry is still there first.
stash@{1}is a position rather than an identity — dropping an entry renumbers
everything below it — so a ref captured seconds earlier can name a different
entry, and acting on it would succeed silently on the wrong one. -
Stash entries in the graph and in the sidebar. Each entry is a row of its
own, hanging off the commit the work was left on, badgedstash@{0}. Only the
entry's first parent is drawn: a stash commit has two or three, and the others
are git's snapshots of the index and of untracked files. -
A Stashes section in the sidebar, alongside local, remote and worktrees —
and since that makes four, every section folds away and remembers it. A
folded section still shows its count.
Changed
-
All four sidebar sections are always shown, empty or not, each saying what
it is for when there is nothing in it. A section that appears only once you are
already using the feature cannot be how anyone discovers it. -
Remote has a Manage button, matching Worktrees and Stashes, and the
toolbar's Remotes button is gone. Two ways into one manager is one too many, and
the toolbar's other three buttons do something where that one opened
something. -
The branch filter is always shown. It appeared only above eight branches,
which made it look like a feature that comes and goes — and the repository where
you go looking for a filter is the one you have just cloned. -
The extension activates on startup rather than waiting for its panel to be
opened. Blame lives in the editor, and an extension that is not running cannot
annotate one. -
Hovering a commit no longer paints over its own lanes and dots. The rows sit
above the SVG that draws them, so a background on the row covered the graph;
rows are painted from the gutter's edge rightwards now. Selection had the same
bug, hiding three rows of graph on a three-commit selection.
Fixed
-
Stash commits are no longer drawn as ordinary history.
git log --allmeans
every ref underrefs/, andrefs/stashis one — so the top stash entry was in
the graph, and so was the snapshot of the index git hangs off it as a second
parent. That snapshot is a commit nobody wrote, drawn as a merge that never
happened, and it had been there since GitHawk first read--all. -
Blame annotates the file you are looking at, not the repository the graph is
pointed at. It asked the active repository for every file, so in a workspace
holding several, opening a file in any other one rangit blamefrom the wrong
working directory: it failed, and the annotations silently never appeared. A
diff worked, which made it look like a rendering problem rather than a lookup
one. The repository now comes from the file's path, longest root first so a
submodule or a nested worktree wins over its parent.
Internal
-
The integration tier keeps VS Code's throwaway profile under the OS temp
directory rather than inside the checkout. macOS caps a unix socket path at 103
characters and VS Code builds one from that directory, so a checkout a few
characters too deep failed to launch at all, reportinglisten EINVALand
nothing that named the cause. -
scripts/shotVscode.mjsfinds whatever VS Code the test runner last
downloaded. It looked forElectroninside the app bundle, which contains
Code, at a version pinned eight months earlier — so it had been unable to
launch at all.
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.