feat: hover cards for PR and issue links - #417
Merged
Merged
Conversation
Anchors referencing a GitHub pull request or issue (GitHub's issue-link references and markdown links to pull/issues URLs) now show an overview hover card, like user mentions do: state icon and badge (open/merged /closed), title, body excerpt, labels, author and creation date. Data comes from the issues endpoint (serves both kinds, distinguishes merged via pull_request.merged_at) fetched lazily on hover and cached. Cross -referenced timeline events are covered too.
This branch was successfully deployed
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.
Anchors referencing a GitHub pull request or issue (GitHub's issue-link
references and markdown links to pull/issues URLs) now show an overview
hover card, like user mentions do: state icon and badge (open/merged
/closed), title, body excerpt, labels, author and creation date. Data
comes from the issues endpoint (serves both kinds, distinguishes merged
via pull_request.merged_at) fetched lazily on hover and cached. Cross
-referenced timeline events are covered too.