Stops requiring for git integration to show Linear and Jira issues on graph#5008
Merged
Stops requiring for git integration to show Linear and Jira issues on graph#5008
Conversation
sergeibbb
added a commit
that referenced
this pull request
Feb 26, 2026
Previously, graph reference metadata fetching was tied solely to hosting integrations. This change extends that capability to include dedicated issue tracking integrations. The graph now tracks the connection state of issue integrations. If a repository has an issue integration connected, it will attempt to fetch relevant metadata, enriching the graph with issue-related context even when a full hosting integration might not be present or connected. Metadata is reset and updated when issue integration connection states change, ensuring the graph accurately reflects available data. (#4640, #5008)
f791e8c to
829c907
Compare
There was a problem hiding this comment.
Pull request overview
Extends the Commit Graph’s ref-metadata enrichment so it can be fetched when an issue-tracker integration (e.g., Jira/Linear) is connected, even if no Git hosting integration is connected—addressing #4640.
Changes:
- Allows missing refs metadata requests when either a hosting integration is connected for the repo or an issue integration is connected.
- Tracks issue integration connection state and resets/updates graph refs metadata when that state changes.
- Adds a changelog entry documenting the fix for Jira/Linear graph enrichment behavior.
Reviewed changes
Copilot reviewed 2 out of 2 changed files in this pull request and generated 3 comments.
| File | Description |
|---|---|
| src/webviews/plus/graph/graphWebview.ts | Adds issue-integration connection tracking and relaxes metadata-fetch gating to include issue integrations. |
| CHANGELOG.md | Documents the fix for issue enrichment visibility on the Commit Graph without hosting integration connection. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
🤖 Augment PR SummarySummary: Extends Commit Graph ref metadata enrichment to work with dedicated issue integrations (e.g., Jira/Linear), not just Git hosting integrations. Changes:
Technical Notes: Uses the integrations service connection events plus a cached connection-state check to decide whether ref metadata fetching should run. 🤖 Was this summary useful? React with 👍 or 👎 |
sergeibbb
added a commit
that referenced
this pull request
Feb 26, 2026
Previously, graph reference metadata fetching was tied solely to hosting integrations. This change extends that capability to include dedicated issue tracking integrations. The graph now tracks the connection state of issue integrations. If a repository has an issue integration connected, it will attempt to fetch relevant metadata, enriching the graph with issue-related context even when a full hosting integration might not be present or connected. Metadata is reset and updated when issue integration connection states change, ensuring the graph accurately reflects available data. (#4640, #5008)
829c907 to
cf61850
Compare
sergeibbb
added a commit
that referenced
this pull request
Feb 26, 2026
Previously, graph reference metadata fetching was tied solely to hosting integrations. This change extends that capability to include dedicated issue tracking integrations. The graph now tracks the connection state of issue integrations. If a repository has an issue integration connected, it will attempt to fetch relevant metadata, enriching the graph with issue-related context even when a full hosting integration might not be present or connected. Metadata is reset and updated when issue integration connection states change, ensuring the graph accurately reflects available data. (#4640, #5008)
cf61850 to
272551b
Compare
sergeibbb
added a commit
that referenced
this pull request
Feb 26, 2026
Previously, graph reference metadata fetching was tied solely to hosting integrations. This change extends that capability to include dedicated issue tracking integrations. The graph now tracks the connection state of issue integrations. If a repository has an issue integration connected, it will attempt to fetch relevant metadata, enriching the graph with issue-related context even when a full hosting integration might not be present or connected. Metadata is reset and updated when issue integration connection states change, ensuring the graph accurately reflects available data. (#4640, #5008)
272551b to
5d7fe47
Compare
… graph Previously, graph reference metadata fetching was tied solely to hosting integrations. This change extends that capability to include dedicated issue tracking integrations. The graph now tracks the connection state of issue integrations. If a repository has an issue integration connected, it will attempt to fetch relevant metadata, enriching the graph with issue-related context even when a full hosting integration might not be present or connected. Metadata is reset and updated when issue integration connection states change, ensuring the graph accurately reflects available data. (#4640, #5008)
5d7fe47 to
30dd895
Compare
ianhattendorf
approved these changes
Feb 27, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Solves: #4640
Previously, graph reference metadata fetching was tied solely to hosting integrations. This change extends that capability to include dedicated issue tracking integrations.
The graph now tracks the connection state of issue integrations. If a repository has an issue integration connected, it will attempt to fetch relevant metadata, enriching the graph with issue-related context even when a full hosting integration might not be present or connected.
Metadata is reset and updated when issue integration connection states change, ensuring the graph accurately reflects available data.
Checklist
Fixes $XXX -orCloses #XXX -prefix to auto-close the issue that your PR addresses