How does GitLens connect commits, pull requests, and issues inside VS Code?
Modern development workflows involve more than just code. Pull requests, issues, and tickets represent the context behind code changes, feature discussions, and bug tracking.
However, navigating between these pieces of information can be slow when developers have to constantly switch between their editor, repository hosting platforms, and issue trackers.
GitLens addresses this by connecting commits, pull requests, and issues directly inside the IDE. This helps developers stay focused in their editor without losing context about why changes were made.
| Feature | Description |
|---|---|
| Branch Cards (Home View) | Each branch card in the GitLens Home view displays the associated pull request and linked issue, including PR title, status, and issue references. |
| Launchpad (Pro) | Centralized dashboard listing pull requests needing attention, with direct links to PR details, diffs, and related issues. |
| Start Work Command | Creates a new branch directly from an issue, automatically associating the branch with that issue for full traceability. |
| Issue Navigation | GitLens links issue references in commits and branch names to their corresponding tickets in connected issue trackers. |
| PR Details View | Opens a detailed pull request view inside the IDE, including file diffs, reviewer status, and comments. |
GitKraken MCP
GitKraken Insights
Dev Team Automations
AI & Security Controls




