Skip to content

Git Vertex VS Code Extension v1.40.0

Choose a tag to compare

@github-actions github-actions released this 04 Nov 18:16
9c4379e

Git Vertex VS Code Extension v1.40.0

Added

  • A review by the model before the pull request is opened. In a comparison of two branches, Review with AI has the model read the diff and comment as a reviewer would — risks such as an error now swallowed or a behaviour changed without a test, and leftovers such as debug output or a TODO added. Each comment sits under the line it is about, in the model's colour, and can be dismissed; a comment about a file as a whole sits under its name. Nothing is sent until you ask, and nothing is posted anywhere. When the diff is too large to send whole, the review says which files it read only in part and which it did not read. The model, its instructions and how much of the diff it reads are set under Settings › AI Assistant › Review before the pull request. (#265)
  • Restore several files of a commit at once. A file's menu in a commit's file list offers Restore All N Files of This Commit…, or, with a filter typed, Restore the N Files Shown…, beside the single-file restore. A file the commit deleted is left out — it has no version there to put back. As with one file, it asks first, and the result lands as pending changes you can read before keeping them. (#69)
  • Compare folders in your external diff tool. Compare Working Tree with Revision…, Compare Working Tree with HEAD, and, from a graph row's menu or the palette, Compare Folders with Parent and Compare Folders with Working Tree open two folders in the tool set in Settings › External tools — Beyond Compare, Meld, Kaleidoscope or any tool that compares folders. Each folder holds only the files the comparison touches, as they are on that side: an added file is absent on the left, a deleted one on the right, and a renamed file appears under both names. Nothing is checked out. Without a tool set, the command says so and opens the settings. (#79)
  • The Overview shows the work in every worktree. Below the card of the branch on screen, a card for each branch checked out in another worktree says where it is, how it stands against its upstream, whether it has uncommitted changes, and its pull request; a click shows its tip in the graph, a double-click opens that worktree. A right-click on any card, the current one included, opens the branch's own menu. RECENT walks back a page at a time — past a month, to a quarter, a year, then everything — and Show older appears whenever there is older work, not only when the list is empty. (#279)
  • Write / Preview on every markdown field of GitHub. The comment box and the description editor of an issue or a pull request, and the body of the pull request and issue composers, gain a Preview tab that draws the draft with the renderer the posted text is read with. The field is only hidden while you look, so the caret and the undo history are where you left them, and a field emptied by posting is back on Write. (#337)
  • Squash several commits into one, from the graph. Select a run of commits with shift-click or ctrl/cmd-click, right-click it, and Squash N Commits into One… opens the interactive rebase with the plan already made — the oldest picked, the others squashed into it, git's combined message ready to edit. Nothing is rewritten until you launch it there. A selection that cannot be folded keeps the row, disabled, saying why: commits with a gap between them, on another branch than the checked-out one, down to the first commit, or with a merge the rebase would flatten. (#69)
  • Open All Changes, for a branch, a stash or a pull request. One row in each of their menus opens every file they change in the editor's multi-file diff, at once. A branch is read from where it forked from the checked-out branch (the checked-out branch, from the repository's merge target); a stash against the commit it was made on, its untracked files included; a pull request is fetched and read from where it left its base on the remote. An added file opens with no left side and a deleted one with no right, instead of an empty document on one side, and a renamed file opens its old name on the left. (#284)
  • Compare a file with any revision. Three commands on an editor tab's menu and in the palette: Open Changes with Revision… leads with the commits that touched the file, Open Changes with Branch or Tag… with the repository's branches and tags, and Open File at Revision… opens the file as it was. The picker takes anything git does, too — a hash, HEAD~3, main@{yesterday} — and checks it before opening; a revision where the file does not exist says so instead of opening an empty side. From a revision already open, the comparison is against that revision. (#79)
  • Browse the repository at any commit, as a folder. Browse Repository at Revision… adds the whole tree, as it was at that commit, to the Explorer — read-only, read straight from git's objects, with nothing checked out and the working tree untouched; Browse Repository Before Revision… opens it as it was just before the commit. Each has an in New Window variant, and a graph row's menu offers all four for its own commit without asking. Search, go to file and the editors work on it as on any folder; a submodule shows as an empty folder, as it does in a checkout that has not run submodule update. (#72)

Installe le VSIX directement :

code --install-extension git-vertex-1.40.0.vsix

Ou cherche Git Vertex dans le Marketplace VS Code.

🔗 VS Code Marketplace
🔗 Open VSX