Allow opening git commit view via URI scheme #43341
Merged
agu-z merged 3 commits intozed-industries:mainfrom Dec 17, 2025
Merged
Allow opening git commit view via URI scheme #43341agu-z merged 3 commits intozed-industries:mainfrom
agu-z merged 3 commits intozed-industries:mainfrom
Conversation
8b9ad00 to
89faacb
Compare
implement parsing and handling of git commit URIs to navigate directly to commit views from external links
89faacb to
a3316b9
Compare
Contributor
|
@schpet This is great! After considering several options, we decided to go with the |
Contributor
Author
|
@agu-z oh wonderful, thanks so much. as someone who bounces between ghostty and zed this is going to really allow me to review diffs a lot more easily! |
HactarCE
pushed a commit
that referenced
this pull request
Dec 17, 2025
Add support for `zed://git/commit/<path-to-repo>#<sha>` (**EDIT:** now changed to `zed://git/commit/<sha>?repo=<path>`) URI scheme to access the git commit view implement parsing and handling of git commit URIs to navigate directly to commit views from external links. the main use case for me is to use OSC8 hyperlinks to link from a git sha into zed. this allows me e.g. to easily navigate from a terminal into zed **questions** - is this URI scheme appropriate? it was the first one i thought of, but wondering if `?ref=<some sha>` might make more sense – the git/commit namespace was also an equally arbitrary choice <details> <summary>video demo showing navigation from zed's built in terminal</summary> https://github.com/user-attachments/assets/18ad7e64-6b39-44b2-a440-1a9eb71cd212 </details> <details> <summary>video demo showing navigation from ghostty to zed's commit view</summary> https://github.com/user-attachments/assets/1825e753-523f-4f98-b59c-7188ae2f5f19 </details> Release Notes: - Added support for `zed://git/commit/<sha>?repo=<path>` URI scheme to access the git commit view --------- Co-authored-by: Agus Zubiaga <agus@zed.dev>
rtfeldman
pushed a commit
that referenced
this pull request
Jan 5, 2026
Add support for `zed://git/commit/<path-to-repo>#<sha>` (**EDIT:** now changed to `zed://git/commit/<sha>?repo=<path>`) URI scheme to access the git commit view implement parsing and handling of git commit URIs to navigate directly to commit views from external links. the main use case for me is to use OSC8 hyperlinks to link from a git sha into zed. this allows me e.g. to easily navigate from a terminal into zed **questions** - is this URI scheme appropriate? it was the first one i thought of, but wondering if `?ref=<some sha>` might make more sense – the git/commit namespace was also an equally arbitrary choice <details> <summary>video demo showing navigation from zed's built in terminal</summary> https://github.com/user-attachments/assets/18ad7e64-6b39-44b2-a440-1a9eb71cd212 </details> <details> <summary>video demo showing navigation from ghostty to zed's commit view</summary> https://github.com/user-attachments/assets/1825e753-523f-4f98-b59c-7188ae2f5f19 </details> Release Notes: - Added support for `zed://git/commit/<sha>?repo=<path>` URI scheme to access the git commit view --------- Co-authored-by: Agus Zubiaga <agus@zed.dev>
LivioGama
pushed a commit
to LivioGama/zed
that referenced
this pull request
Jan 20, 2026
Add support for `zed://git/commit/<path-to-repo>#<sha>` (**EDIT:** now changed to `zed://git/commit/<sha>?repo=<path>`) URI scheme to access the git commit view implement parsing and handling of git commit URIs to navigate directly to commit views from external links. the main use case for me is to use OSC8 hyperlinks to link from a git sha into zed. this allows me e.g. to easily navigate from a terminal into zed **questions** - is this URI scheme appropriate? it was the first one i thought of, but wondering if `?ref=<some sha>` might make more sense – the git/commit namespace was also an equally arbitrary choice <details> <summary>video demo showing navigation from zed's built in terminal</summary> https://github.com/user-attachments/assets/18ad7e64-6b39-44b2-a440-1a9eb71cd212 </details> <details> <summary>video demo showing navigation from ghostty to zed's commit view</summary> https://github.com/user-attachments/assets/1825e753-523f-4f98-b59c-7188ae2f5f19 </details> Release Notes: - Added support for `zed://git/commit/<sha>?repo=<path>` URI scheme to access the git commit view --------- Co-authored-by: Agus Zubiaga <agus@zed.dev>
LivioGama
pushed a commit
to LivioGama/zed
that referenced
this pull request
Jan 20, 2026
Add support for `zed://git/commit/<path-to-repo>#<sha>` (**EDIT:** now changed to `zed://git/commit/<sha>?repo=<path>`) URI scheme to access the git commit view implement parsing and handling of git commit URIs to navigate directly to commit views from external links. the main use case for me is to use OSC8 hyperlinks to link from a git sha into zed. this allows me e.g. to easily navigate from a terminal into zed **questions** - is this URI scheme appropriate? it was the first one i thought of, but wondering if `?ref=<some sha>` might make more sense – the git/commit namespace was also an equally arbitrary choice <details> <summary>video demo showing navigation from zed's built in terminal</summary> https://github.com/user-attachments/assets/18ad7e64-6b39-44b2-a440-1a9eb71cd212 </details> <details> <summary>video demo showing navigation from ghostty to zed's commit view</summary> https://github.com/user-attachments/assets/1825e753-523f-4f98-b59c-7188ae2f5f19 </details> Release Notes: - Added support for `zed://git/commit/<sha>?repo=<path>` URI scheme to access the git commit view --------- Co-authored-by: Agus Zubiaga <agus@zed.dev>
LivioGama
pushed a commit
to LivioGama/zed
that referenced
this pull request
Feb 15, 2026
Add support for `zed://git/commit/<path-to-repo>#<sha>` (**EDIT:** now changed to `zed://git/commit/<sha>?repo=<path>`) URI scheme to access the git commit view implement parsing and handling of git commit URIs to navigate directly to commit views from external links. the main use case for me is to use OSC8 hyperlinks to link from a git sha into zed. this allows me e.g. to easily navigate from a terminal into zed **questions** - is this URI scheme appropriate? it was the first one i thought of, but wondering if `?ref=<some sha>` might make more sense – the git/commit namespace was also an equally arbitrary choice <details> <summary>video demo showing navigation from zed's built in terminal</summary> https://github.com/user-attachments/assets/18ad7e64-6b39-44b2-a440-1a9eb71cd212 </details> <details> <summary>video demo showing navigation from ghostty to zed's commit view</summary> https://github.com/user-attachments/assets/1825e753-523f-4f98-b59c-7188ae2f5f19 </details> Release Notes: - Added support for `zed://git/commit/<sha>?repo=<path>` URI scheme to access the git commit view --------- Co-authored-by: Agus Zubiaga <agus@zed.dev>
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
3 participants
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.
Add support for
zed://git/commit/<path-to-repo>#<sha>(EDIT: now changed tozed://git/commit/<sha>?repo=<path>) URI scheme to access the git commit viewimplement parsing and handling of git commit URIs to navigate directly to commit views from external links. the main use case for me is to use OSC8 hyperlinks to link from a git sha into zed. this allows me e.g. to easily navigate from a terminal into zed
questions
?ref=<some sha>might make more sense – the git/commit namespace was also an equally arbitrary choicevideo demo showing navigation from zed's built in terminal
zed-uri-within-zed.mp4
video demo showing navigation from ghostty to zed's commit view
zed-uri-commit-video.mp4
Release Notes:
zed://git/commit/<sha>?repo=<path>URI scheme to access the git commit view