Git Vertex VS Code Extension v1.26.0

Git Vertex VS Code Extension v1.26.0

Changed

• "What's new" is written for you, not for the repository. After an update the extension opened CHANGELOG.md in a markdown preview — the whole file, every version back to 1.0.0, in Added / Changed / Fixed sections aimed at whoever reads the source. It now opens the note for the version you just got, in the same view the desktop app has always used, with Git Vertex: What's New in the command palette to re-read it later. Every past version has a note too, so the history is browsable rather than starting from today.
• The panel's context menu speaks the same language as the desktop app. Its wording comes from the extension manifest, the desktop's from the shared string catalogue, and nothing kept the two in step — six actions had drifted, including the one that detaches HEAD (Switch to Commit here, Check out this commit there) and the three reset modes. A test now compares both catalogues.
• Actions that open an input carry …; the ones that act immediately do not.

Added

• Sign in to GitHub without minting a token. The panel offered a Personal Access Token and nothing else: the desktop app signs in through an OAuth proxy and a gitgui:// deep link, neither of which exists here. So everything already shipped behind a token — creating a pull request, the PR and issue lists, the #123 cards on private repositories — was gated behind a trip to github.com. Sign-in now goes through VS Code's own GitHub provider, the same one Settings Sync and Copilot use, so for most people it is confirming an account they are already signed in to rather than logging in again.
• You choose which account. VS Code remembers the account an extension last used and reuses it silently from then on, so a personal and a work GitHub account signed in side by side would give you whichever we happened to land on first, with no way back. Signing in now asks, every time you ask it to.
• The token stays as a fallback, for editors that do not bundle that provider — VSCodium and other OSS builds — and for anyone who would rather hand over a narrowly scoped token. If the provider is missing the panel says so and points at the token field, instead of opening a dialog that never appears.
• Disconnect means Git Vertex stops using your account. Your GitHub session belongs to VS Code, and no extension can revoke it — so the panel signs itself out and leaves the account where it is, saying so and pointing at the Accounts menu rather than appearing to do nothing. Signing in again picks it straight back up. Settings also states where the account came from — Signed in through VS Code or a token we hold — because the two behave differently when you disconnect.
• The Agents view in the rail actually lists agents. The robot icon opened an empty section from the day the rail shipped: finding running agents was a ps walk the desktop did in its main process, and this side never had one. It does now — the same walk, so Claude Code, aider, Codex, Gemini, Amp and Goose show up here as they do on the desktop, and worktree rows get the "an agent is working here" badge that goes with them.
• #123 in a commit message opens its hover card. The link was already there, in the graph and in the commit panel, but the card behind it never resolved: it asked the host for the issue and the host had no answer, so it fell back to the bare number. It now shows the title and whether the issue or request is open, closed or merged. Public repositories answer without a token.

Fixed

• Two commands were both called "Open in Git Vertex", and the second was never filtered out of the command palette — so the palette listed the same name twice, for two entries that did the same thing when invoked without a file. The file-scoped one is now a context-menu action only, and a test fails on any two commands sharing a title.
• A command title leaked an implementation detail: Toggle Interactive Rebase Editor (sequence.editor + core.editor). The parenthetical named the two git config keys the command writes, which tells a user nothing about what will happen.
• Nothing stopped the panel from showing a button it had already declared dead. The parity test made every window.gitAPI method be classified — implemented here, or written down as desktop-only — but it never looked at the screen, and both kinds answer not-implemented at runtime. So a classified method could stay wired to a visible control, and three did: the two above, plus Settings asking the host for an updater state VS Code has no updater for. Each failed silently, because every one of those call sites swallowed its own error. A second test now walks the panel's real module graph and fails on any call it can reach, and both tests run on every pull request instead of only before a release.

---

Installe le VSIX directement :

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

Ou cherche Git Vertex dans le Marketplace VS Code.

🔗 VS Code Marketplace
🔗 Open VSX