Repository navigation
BranchDeck 1.0.2
BranchDeck 1.0.2
Two things the window can now tell you before you have to find out the hard way, and a run of fixes
for what it quietly got wrong whenever somebody else touched the repository.
-
You can see how many lines are in your working tree.
12 file changesnever said whether that
was a rename sweep or a rewrite. The header now reads12 file changes +124 −37, and Unstaged and
Staged each carry their own pair — so what you are about to commit has a size, not just a count.
New files count as every line they hold; binary files, renames and mode changes have no lines to
report and say nothing rather than+0 −0. -
Tokens can tell you before they expire. The sign-in form has an optional Expires on field —
copy the date the service shows next to the token — and BranchDeck warns you a week ahead instead
of letting you find out on the morning it stops. If a service refuses an account outright, that is
now written on the account in Accounts rather than appearing once in a message and vanishing. -
Compare and Open in editor are told apart. The two buttons in the file header drew almost the
same icon. Compare has its own now — and it only appears when you actually have a difftool set up,
instead of being a button that quietly did nothing. -
Long lines are readable side by side. A line wider than its column used to be cut off with
nothing to say so — and since the change is usually at the end of a long line, that was often the
part you could not see. The diff now scrolls sideways, both halves together. -
Split view no longer shows a wall of green where nothing was added. When a block of lines is
deleted and one line replaces them, the empty side of each row was painted as if it were an
addition. That space is now hatched, the way it is in every other side-by-side diff: the lines are
still paired across the two sides, and the gap reads as deliberate rather than as a hole. -
A commit made outside BranchDeck now appears on its own. Commit from a terminal, your IDE or a
coding agent, and the new commit was missing from the history until you switched branches and back.
BranchDeck was watching the repository, but it only ever re-read the working tree — and a commit
leaves the working tree exactly as it was, so there was nothing there to see. It now checks whether
the repository's branches still match the history on screen, and reloads when they do not. -
The reload stays out of your way. No spinner, no toast, and an open diff or a selected commit
stays where it was. -
Fetching, branching and resetting from outside are covered too, along with the branch labels and
the graph that go with them. -
Update all stays in the folder you filtered to. Narrow the repository list to one clone folder,
press Update all, and the batch used to open on every repository saved on the machine. It now opens
on the folder you were in — and the filter stays put when you close the picker. -
A background fetch no longer closes the file you are reading. With automatic fetching on, the
open diff disappeared every few minutes and you had to click the file again. The timer, the fetch
as a repository opens, and Update all now all reload quietly, leaving what you are reading alone. -
Signing in to Azure DevOps through a browser works everywhere. On some machines it failed with
could not read Username for 'https://dev.azure.com'instead of opening one. BranchDeck was
sending the organization, but Git only passes it on to the credential manager when a particular
setting is present — and without the organization, Azure DevOps sign-in cannot work out which
account you mean. BranchDeck no longer depends on that setting being there. If a sign-in does go
wrong, the message now says what went wrong rather than what Git tried to do about it.
Generating a commit message on a big change is worth doing again.
- The message no longer breaks off in the middle of a sentence. On a large staged change the
description used to stop mid-thought — and BranchDeck reported it as a success, because the reply
was technically well-formed. An unfinished sentence is now dropped, and you are told it happened. - The whole change is described, not its first two files. A third of what the model was given to
read was line numbers, file paths it already had, and unchanged lines. With those gone and the
reading budget shared so a small file keeps all of its diff, a 33-file change now comes back
describing three to eight things it does rather than one or two — in half the time. - The subject line ends where a sentence would. No more "…to show how many lines are in the
working". - Choosing a paragraph instead of bullets gets the same care. Prose descriptions were missing
the rules the bulleted ones had, and it showed.
And the help window learned the words you would actually type.
- One word is a question.
gpg,ssh,difftool,whitespace,prune,theme,font,
activity— all of these used to come back empty. There are three new answers behind them
(editors and diff tools, the commit author and signing, the activity log and diagnostics), and the
search now also looks through Settings and offers you the exact switch. - Plurals work.
conflictsfinds whatconflictfinds. - A word reaches the answer it is about.
updatenow answers with updating BranchDeck rather
than with updating every repository, andcommit,rebase,merge,searchandcloneeach
reach their own answer instead of one that merely mentions them.ideno longer answers with a
topic about where clones go, andprno longer offers "Prune on fetch".