Skip to content
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

Emphasize the selected branch(es) #236

Closed
goyzhang opened this issue Dec 20, 2019 · 1 comment
Closed

Emphasize the selected branch(es) #236

goyzhang opened this issue Dec 20, 2019 · 1 comment
Assignees
Labels
backlog Requests that are closed for now, but may be re-opened in the future if more interest is expressed feature request Feature request

Comments

@goyzhang
Copy link

When a repo contains a lot of branches, the git view can be very messy and hard to tell which commits are on the current branch:
image

Is it possible to have an option that make other branches fade out or Bold the selected branch so we have a clear impression at the first look? Sample from gitextension:
image

@goyzhang goyzhang added the feature request Feature request label Dec 20, 2019
@mhutchie mhutchie added the backlog Requests that are closed for now, but may be re-opened in the future if more interest is expressed label Dec 20, 2019
@mhutchie
Copy link
Owner

Thanks for raising this request!

I've just been working on implementing #139, which will "mute" (grey out) the commits not part of the current branch. The muting will be controlled by an Extension Setting just like the existing option to Mute Merge Commits.

To grey out lines in the graph and/or bold them is definitely possible, however it would be extremely complex and time-consuming to achieve. I could only justify the time it would take if a significant portion of users indicate they would gain significant value from it.

As #139 has an extremely similar effect to this request, however is far more reasonable to implement, I'm working to release it first in v1.20.0 (in the next few days). I'll close this request for now and move it to the backlog, as I hope the other feature already mid-development will resolve or significantly ease this issue. I'll gather feedback from users in the weeks after v1.20.0 is released to see if #139 is adequate, or if the additional graph-based emphasis would be valued.

If I have an indication that this graph-based emphasis would be reasonably valued by users (and I feel it justifies the development time & complexity), I'll definitely re-open this feature request and implement it.

Note: If you are another Git Graph user reading this response in the future, and would value graph-based emphasis of the selected branches, please like the first comment on this issue. This will allow me to re-prioritise it based on community interest.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
backlog Requests that are closed for now, but may be re-opened in the future if more interest is expressed feature request Feature request
Projects
None yet
Development

No branches or pull requests

2 participants