Skip to content

View log at git revision #1600

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

Closed
M1cha opened this issue Mar 14, 2023 · 6 comments
Closed

View log at git revision #1600

M1cha opened this issue Mar 14, 2023 · 6 comments
Milestone

Comments

@M1cha
Copy link

M1cha commented Mar 14, 2023

Is your feature request related to a problem? Please describe.
Currently you can only view the log of HEAD, tags, branches and stashes. But I can't enter an arbitrary git hash or an alias(like FETCH_HEAD).

Describe the solution you'd like
Either add a form for pasting a revision or alias, or accept a position argument to gitui similar to the way git log REV works.

@M1cha
Copy link
Author

M1cha commented Mar 14, 2023

I just noticed that you currently can't view the log of a branch, tag, ... without checking it out. So something like that would probably be a requirement for this issue.

@extrawurst
Copy link
Collaborator

well actually if its about the detail view of a specific commit:
Screenshot 2023-03-14 at 13 50 43

that could be done 🧐 its only a problem if you want to jump to that commit in the log view if its not in the current branch lineage

@M1cha
Copy link
Author

M1cha commented Mar 14, 2023

Yea and that's exactly what I want to do :D
I guess I also misinterpreted the menu in the log view since I expected those to be for viewing and not for switching. Both are obviously useful features for gitui, the question is just if one would expect modifying options within the log view 🤔

@extrawurst
Copy link
Collaborator

Yea and that's exactly what I want to do :D

then its more like a dupe of #506

I guess I also misinterpreted the menu in the log view since I expected those to be for viewing and not for switching

can you specify?

@extrawurst extrawurst added this to the v0.25 milestone Aug 22, 2023
@extrawurst
Copy link
Collaborator

#1818 will deal with the go-to-sha-in-the-current-log part.
a follow-pr could figure out that a sha is in the repo but not in the current log and just open the commit details view for that one as a popup

@extrawurst extrawurst mentioned this issue Aug 23, 2023
4 tasks
@extrawurst
Copy link
Collaborator

solved via #1818

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Projects
None yet
Development

No branches or pull requests

2 participants