-
Notifications
You must be signed in to change notification settings - Fork 141
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
forgit log
cannot diff merge commits
#416
Comments
carlfriedrich
added a commit
to carlfriedrich/forgit
that referenced
this issue
Dec 29, 2024
Use the new command in git log enter. This fixes the display of diffs for merge commits. Fixes wfxr#416.
15 tasks
carlfriedrich
added a commit
to carlfriedrich/forgit
that referenced
this issue
Jan 1, 2025
Use the new command in git log enter. This fixes the display of diffs for merge commits. Fixes wfxr#416.
carlfriedrich
added a commit
to carlfriedrich/forgit
that referenced
this issue
Jan 4, 2025
Use the new command in git log enter. This fixes the display of diffs for merge commits. Fixes wfxr#416.
carlfriedrich
added a commit
to carlfriedrich/forgit
that referenced
this issue
Jan 4, 2025
Use the new command in git log enter. This fixes the display of diffs for merge commits. Fixes wfxr#416.
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Check list
Environment info
Problem / Steps to reproduce
Merge commits cannot be diffed from within
forgit log
.Steps to reproduce:
Afterwards call
git forgit log
and try to view the merge commit by pressingenter
. It does not work (immediately returns).The reason is that our current implementation using the
^!
operator on the commit does not work for merge commits. According to this stack overflow answer there are only three ways to correctly show the diff for a merge commit:A quick fix would be to change our implementation to the third option. The cleaner solution IMO, though, would be to implement a
forgit show
command. I am planning to do the latter.The text was updated successfully, but these errors were encountered: