Skip to content

v0.21.0

Pre-release
Pre-release

Choose a tag to compare

@github-actions github-actions released this 29 Oct 12:56
· 68 commits to main since this release

Added

  • Images in the diff: a changed image (PNG, JPEG, GIF, WebP, BMP, ICO, AVIF, and TGA, common for game textures) shows as the pictures before and after, side by side, with their size in pixels and bytes (two of the same size can also be compared with a divider swiped across or one over the other), instead of "Binary file" — for uncommitted changes, commits, file history and pull request reviews. A conflicted image shows its current and incoming sides in the conflict editor, to take one seeing them. Images in Git LFS show too, from the files downloaded here (nothing is fetched); one not downloaded says so.
  • Delete branches whose remote branch is gone: when branches were deleted on the server (often once their pull requests were merged), a button in the LOCAL header (and the menu of such a branch) lists them to delete at once. Only branches that had a remote branch are listed, never one that was not pushed, nor the one checked out; a branch with commits found on no other branch comes unchecked and says how many (a squash merge leaves them so). One Undo brings them all back.
  • Pull, merge, rebase, cherry-pick and revert with uncommitted changes in the way: instead of git's error, the app names the files (a rebase refuses for any change) and offers to stash them and bring them back once it is done, or only to stash them. When the operation stops for conflicts, the changes wait in the stash and the app says so. Undo goes back with the changes in one step.
  • Checkout with uncommitted changes in the way: when changes would be overwritten by switching branch (or checking out a commit or a pull request), the app names the files and offers to stash them and check out, take them along (stashed and applied on the other branch; where they clash, the files are left with conflicts and the stash is kept), or discard those files and check out, instead of git's error. Undo goes back to where you were, with the changes, in one step.
  • Interactive rebase with merges: a range of commits with merges among them no longer refuses the interactive rebase. The merges are kept as they are (git's own --rebase-merges plan), shown as fixed rows, with a dashed line where a merged branch starts; each commit can still be reworded, edited, squashed, fixed up or dropped. Commits are not moved across branches there (without merges, reordering is as before).
  • Several consoles in the terminal: the + in its header opens another console of the repository in a tab of its own, each with its shell and what it ran; the × on a tab closes it. URLs in the output (the one git push prints to open a pull request, for example) open in the browser with Ctrl+click (⌘+click on macOS). The terminal's font size is in Settings → External tools.
  • Undoing a hard reset brings back the changes it dropped, staged and not, along with the branch.
  • Undo a discard, and stashes: discarded changes (whole files, new files, a hunk, or everything) come back with Undo (Ctrl+Z), exactly as they were, and Redo discards them again. Saving, applying, popping and deleting a stash can be undone too. Only files over 50 MB are not kept for it (a game's assets can be gigabytes): then the app says that action cannot be undone. Undo refuses, as ever, when a file was edited since.

Fixed

  • Stash no longer says there is nothing to stash for a change made a moment before the app saw it: git is asked first.
  • The first commit of an empty repository can be undone: its files are left staged, and Redo commits them again.
  • Undoing a merge commit made with --no-ff (one that could have fast-forwarded) brings the merge back as such: committing it again makes a merge, not a plain commit of the other branch.
  • An open diff follows a file that became untracked (git rm --cached in a terminal) or tracked again, instead of showing no changes.
  • Accounts on a server of your own: Settings → Accounts says how to add GitHub Enterprise, a GitLab of your own or Gitea (Add account, with the server as host and a token created there).
  • Undoing a stash of all changes (or a discard of everything) no longer risks a change the app had not shown yet: the copy kept for undo was made from the files of the last refresh, so a change made just before (by another program, or right after an undo) could go with the stash and not come back. The copy is now made from what git sees at that moment.
  • The ✕ beside a branch says what it means on hover: its remote branch no longer exists (deleted on the server, often once its pull request was merged), and the branch keeps its commits.
  • A stash that clashes with the files when applied says that they are left with conflicts to resolve and that the stash is kept, instead of git's report.
  • Undo no longer takes in what a background fetch brought: tags fetched while a commit (or any action) ran were part of it, and undoing it deleted them. An action now waits for a fetch under way, and none starts until it is done.
  • Installing git-lfs: its progress shows whole lines; where the app cannot install it, the LFS section offers to copy the command (also after the question was turned down); accepting it while the repository is busy says so instead of taking over; closing the tab it installs from asks first (the install goes on).
  • A refused pull request change (closing one without the right to) no longer blames the token alone: the account's role on the project may be what is missing.
  • Signing in with GitHub waits through a dropped connection or a GitHub server error while you enter the code.
  • The changed-file headers fit the narrowest panel: with files checked, the buttons say the action and the count ("Stage (3)", "Discard (3)…", with the whole sentence as a tooltip), so the title stays in sight; in Spanish "Quitar selección" no longer reads as "deselect". The divider between the lists moves with the arrow keys too.

Code signing policy · Privacy policy