Git Vertex VS Code Extension v1.27.0

Git Vertex VS Code Extension v1.27.0

Added

• References in commit messages become links — yours, not just #123. Settings › GitHub takes a list of patterns: a prefix (JIRA-) and a URL with <num> in it. Teams that track work anywhere but GitHub issues were reading their own ticket numbers as plain text.
• Add a co-author to a commit, from the commit options. The panel already wrote a Signed-off-by trailer and already read co-authors to show their avatars; this is the half that was missing. The candidates are whoever has committed here recently.
• Right-click a file in the staging list to copy its path or its name. VS Code's own copy-path commands act on the explorer, never on our list.
• Step through a file's changes with Go to Next Change / Go to Previous Change (alt+. / alt+,): each stop is a different commit, so a file written in four sittings has four stops rather than one per line.
• Clear File Blame Annotations as its own command, for when you want them gone and cannot remember whether they are on.
• Right-click a file in a commit: open it on the remote, or copy its link. The panel knew the file and the commit it belonged to, and could do nothing with either. The link is built at that commit, so the line numbers it points at are the ones you were looking at.
• Copy a link to a comparison, from the compare tab — and to a pull request or an issue, from the GitHub tab.
• Open Branches on Remote in the branch menu, one level up from Open Branch on Remote.
• Copy a link to the lines you selected. Right-click in the editor: Copy Link to These Lines gives the URL your reviewer can open, with the selection already highlighted. Open This File on Remote is the same calculation with the other verb, and the editor tab's menu carries a whole-file variant. The link points at the commit that last touched the file rather than at a branch — a link to main shows something else next week, which is rarely what someone sharing line 40 meant.
• Copy a link to a branch or a commit, from the panel. The desktop could; the panel could only open a commit on the remote. Both products now build every link from one place, which is also what makes the next one possible.

Changed

• Links are built from your remote, not from github.com. The URL was written out by hand in six places with the host hardcoded in every one, so a repository on GitLab, Bitbucket, or a self-hosted GitHub produced a link to a page that does not exist. One builder reads the remote and knows the shapes; GitLab's and Bitbucket's are declared from their published forms rather than assumed.
• We ask for one GitHub permission instead of two. read:user was never needed — the profile call answers with the public profile for any token, and the login and avatar are all the settings page shows. Beyond the hygiene, VS Code matches sessions by their exact set of permissions, so asking for less makes it likelier we can reuse an account you have already approved elsewhere.

Fixed

• Signing out of GitHub from VS Code now reaches the panel. Your account lives in VS Code's Accounts menu, and signing out there left Git Vertex's settings showing an account that was gone — until the page was closed and reopened. It was the last place the panel could still be telling you something untrue.
• A revoked token said HTTP 401. A session can be revoked from github.com after we were handed it, and the panel then showed a bare status code next to the avatar and login of the account it had just stopped working for. It now reads as what it is — not signed in — and offers the way back in. A 403 deliberately keeps its status: rate limiting and "you may not do this" are not fixed by signing in again.

---

Installe le VSIX directement :

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

Ou cherche Git Vertex dans le Marketplace VS Code.

🔗 VS Code Marketplace
🔗 Open VSX