Commit Log

[JosephTLyons]

The user should have access to the history of commits.

• Each commit in the history view shows the commit message, author(s), and time.
• Clicking a commit would open the commit diff.
• Allow the commit list to be searched.
• Decorations for tags and branches

Other nice-to-haves, but could be skipped for the initial implementation, and added incrementally:

• Real-time search
• Commit details (as those show up in commit view when clicking)
• Rearranging and squashing of commits
• Creating branches off of commits
• Commit graph

Related:

• Implement file history viewing, including local and Git. #16827

[coolemur]

Gitlense has nice UI.

On leftside list of commits on right side diff of selected commit.
Also, would be nice to have a quick way to checkout selected commit from history (for debugging purposes) - double click on commit in history could check out that commit.

[keybits]

Similarly it would be worth taking insipiration form Sublime Merge.

The commits view is very intuitive and powerful.

[WoodyWoodsta]

My biggest ask - and I ask with my whole heart... That if and when Zed implements this that the graph view is beautiful. IMO, nothing beats Gitkraken's graph view for being able to easily visualise branches and where they go.

Some of the things Gitkraken's view gets right:

• Separated information in columns: branches, graph, commit, sha, date
• Column alignment
• Straight branch lines (not weird angled lines)
• Proper and generous horizontal spread of commits belonging to each branch in the graph view
• Similar colours based on proximity of branches from one another

---

It seems like every other source control solution resorts to something that looks like the below, and it significantly reduces the clarity and how quickly you can understand a graph in a more complex project.

[KaKi87]

Looks like they ignored you. 😭

[kozel-sd]

So many options for the commit list view... My favorite is how it's made in Git Extensions - it derives branches from branch lines instead of commits, which makes the view cleaner in most cases (at least for me 😃):

(note the line to the selected commit).
Everything else, even the Gitkraken's approach, makes me sad.

Is it a good idea to define an API for obtaining Git log info, drawing primitives into the view box and interacting with it, provide a default implementation, and allow users to replace it? Maybe by adding an entry in Settings with the path to a shared library that implements the desired view 🤔

[jmoore34]

I think it would be perfectly acceptable to start with something basic and then iterate on it later

[Sduby22]

hi devs, I would like to introduce some good designs from gitlens:

1. 'commits' tab shows commit history in current branch in Git panel

2. in 'commits' tab, you can select 'commits' / 'branches' / 'remotes' / 'stashes' to view commits from other places

3. you can filter commits by author

4. in 'Inspect' panel, you can view a file's commit history

[douglasrizzo]

Maybe I am just lazy with learning git, but I enjoy the fact that, with GitKraken and the VSCode Git Graph extension, I can checkout, merge, reset, delete, rebase branches, all through the graph.

I find it much faster to do lots of complex operations using the visual aid of the graph than having to look at the commit log, mention commits by hash etc. The ability to run these git commands through the graph could be something to consider in a git graph implementation of Zed.

[CaptainN]

The lack of a git graph in zed is the only thing keeping me from trying it out on a longer term basis.

[gordinmitya]

I think this worth mention https://github.com/lusingander/serie

[WoodyWoodsta]

Stunning!

[gengurke]

I also love https://open-vsx.org/extension/mhutchie/git-graph. Simple but powerful. Would love something similar in Zed (or a Zed extension)

[tediou5]

I found a pull request that already works pretty well for me #39595.
I'm not trying to push the team, I'm just wondering if the team has seen it and if there are any plans to merge it. It looks like it's almost ready to use.

[kobago]

Alternatively, closed PR can be developed in isolation as extension.

[Angelk90]

@JosephTLyons, can you provide us with some guidelines on how to implement the solution?

@zanmato created a PR that you can view here: #39595.

It would be helpful to have an overview of Zed's thinking on this point.

We can also discuss this with the design team to ensure the implementation integrates properly with the rest of Zed.

[dimitrijejankov]

Personally I think the best UI I have ever used is by Meta's Sapling. https://sapling-scm.com/docs/addons/vscode/ this easily beats any pure git extension vscode has.

[MikePryadko]

Any news?

Git without log is... uncomfortably 😢

I've made a commit, but I don't see it: what is commited, but not pushed, what was pulled & etc 😕 and where is branches list? Which branches are on server, which are on my local machine, how to interact with them?

IMHO Computer programs is needed for making human's life simpler! But Zed does this only partially... 😞

[probitcarwyn]

• git: Add graph support #44434

[MikePryadko]

Ok, let's continue using the external tool and wait(

[dDostalker]

I'm pleased to tell you this pull request successfully merged and closed

[juev]

Did you decide anything in the end? Or are you leaving it for now until better times?

[fabianszabo]

Could we add a simple git history view at least?

We already have a simple way to display the last commit including preview on hover and a detail view when clicked.

It would already be a huge help to have the commits listed in a picker.

e.g. branch picker:

It's not a git graph, it's not git lens 2.0, but at least we'd have SOMETHING. 😅

[tediou5]

Hey, everyone who is waiting here. I must announce that the official graph implementation has been merged.
#44434

[onenewcode]

Hey, everyone who is waiting here. I must announce that the official graph implementation has been merged. #44434

Thank you for the reminder.That's great.

[ojpro]

It's live on the preview:
https://github.com/zed-industries/zed/releases/tag/v0.231.1-pre

Thank you Zed Team & All Contributors ❤️

[WoodyWoodsta]

Loving the preview of the commit log graph view!! I have a few comments/asks for future iterations:

• Split tags and branch names away from commit messages
  It's really difficult to scan commit messages and branch names alike when they are mixed within the same column. It also becomes a problem when multiple branch heads exist at the same commit. The commit name is lost
• Truncate long branch/tag names
• Emphasised style for the checked out branch
  Scanning the list, it's unclear where the checked out head is
• Fold remotes for the same branch into the same label
  If multiple remotes have the branch head at the same commit, it would make sense to fold these into the same label/tag UI
• Position HEAD at the left
  Draw the graph such that the branch which is currently checked out renders to the left
• Add uncommitted changes and stashes

Otherwise, it's one step closer from me cancelling my Gitkraken subscription!! Thank you Zed team.

[ojpro]

Also option to filter by username

[JosephTLyons]

Hey all

The git graph has shipped in Zed Stable 0.231!

It covers the essentials listed in this discussion:

• commits with message, author, and time
• click-to-open commit diff
• search
• tag + branch decorations
• commit information panel

The remaining items that haven't been addressed yet (such as rearranging or squashing commits, and creating branches off commits) will be addressed soon, along with other features.

If you'd like to see additional functionality on top of the git graph, feel free to open a new feature request Discussion so we can track each ask individually.

[KaKi87]

Nice !

I'll be grateful to whoever will courageously take the time to make a feature request for every action that can be applied to commits, as the git graph is currently read-only.

[lorenzo-campanile-octo]

This is such great news!! I redownloaded the Zed app yesterday (~15 mins after your message, I came back to this thread after seeing the 1.0 announcement on hackernews). Today I am trying this at work, this was probably the last missing feature that was preventing me from switching to Zed (from VScode). Finally!! 🥳

[Angelk90]

It would be nice to have the timeline.

https://x.com/ruru_1x/status/2068021793173172351?s=20