-
Notifications
You must be signed in to change notification settings - Fork 29.4k
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
Git source control is showing the whole history under "Incoming/Outgoing" when the working tree is clean #224517
Comments
Did you see https://code.visualstudio.com/updates/v1_92#_incomingoutgoing-changes-graph about the new history graph which is the default since 1.92 released today? |
@gjsjohnmurray thanks for the link. I came here looking to find out how to turn it off. The release notes say tell us how you like it. Not sure where to do that. I would have loved it if it was in a collapsible/accordion section like all the others. I really only want to see commits that aren't yet pushed/pulled all the time (like it used to do). The section naming is now misleading; I'd expect "Incoming/Outgoing" to be empty once I've pulled/pushed(?) Would it be possible to describe use case(s) where a dev would want to see historical commits all the time? Maybe I'm using git in an unusual manner(?) |
I do appreciate the feature, but I'd agree that it really should be an accordion section. Scrolling through the staging area now flies off into the commit history instead of hitting a hard stop at the last unstaged file. |
I welcome the feature to display the Git Commit Graph as it is something I have wanted for a long time. However, I strongly believe that these should be displayed as an independent section like GitLens and not within the Source Control. |
What is more, it show up on a repo which I'll never pull or push, no upstream set. |
I have the same issue. Would be nice to be able to toggle off or hide, is very invasive at the moment. Version: 1.92.0 (Universal)
|
If you have many changes, this slows down VS Code incredibly too. |
@georgerdpdmg the |
Thank you all for the feedback! The thinking behind showing the changes in the main Source Control view is that these changes are related to your inner loop (outgoing changes, incoming changes, and changes to the base branch in case one exists). I hear you that this information can be distracting if you are used to the Source Control view being empty when there are no pending changes. We are considering making the section collapsible though if we were to collapse it, I would rather move this information into a separate view. Please keep the feedback coming. Thank you! |
Can this be made opt-in? It's really hard to read, adds clutter to the UI, I have no idea what it's showing me and adds no value to me on a first glance. Maybe if I was looking for it specifically it would be useful, but as is it's just distracting. |
@ricardograca-scratch please see https://code.visualstudio.com/updates/v1_92#_incomingoutgoing-changes-graph for mention of the setting to disable it. |
@gjsjohnmurray Thank you, much better now with Thank you @lszomoru, if in a future release is going to become UI toggle-able I will enabled it back because it has value. |
Ya, i dont like this feature. |
Same here. It just felt all cumbersome and poorly organized. |
@lszomoru It seems to have performance issues. I upgraded today to v1.92.0 and had a couple times that VSC was (temporary) unresponsive when switching/merging branches. Also I think it's confusing to see this graph in the same spot where you normally only see the differences with the remote branch. I think it would be better if it's separate (like the timeline in the explorer). |
I was using it before, but after the update it feels slower, probably because now shows too the main branch where there are lots of merge commits 🤔 |
I have about 15 repos all under the same workspace. This makes that tab incredibly noisy and hard to navigate without adding any value to my workflow. Why on earth wasn't there a simple "hide" button added when this was released? Further: on the first repo the history spans 6 "pages" on that sidebar. The other repos show far less, but interestingly, when I've done a sync on the other repos the history disappears (yay). And yet the 6 pages of pointless history on the first repo is always shown PLEASE let us hide this. It's absolutely killing my productivity and I'm finding I'm making mistakes having to hunt through the jungle. |
@gjsjohnmurray I owe you a beer. |
Thanks for sharing that setting to disable it but it would be better if we could toggle it right in the source control panel instead. I liked how it worked before where I would see my outgoing commits before pushing them as it gave me visibility without making the list take up the entire panel like it does now. |
To those who want to toggle this 'History Graph' off:
Search tags (hopefully to help other developers searching about this feature): |
Is there somehow the option to limit the number of entries in the history? I would like something like a head (top 5) or configurable via settings to the top x. |
I agree with others who say that this is too noisy and should at lease be collapsible, if not disabled by default. I was searching around for the option to disable and now that I've disabled it it's way better and I can focus on actual code that is not yet pushed or pulled. I agree that it can be useful, but either collapsed or in another view. |
I've just come across this change today. I have to say as per comments here it's noisy/confusing . I'm also unsure of any actual use case where it would be in any way useful. Should have been an opt in for those that want vscode clutter. |
I do like it, though MUST add something that limits how many history entries are shown for each repo. |
When this feature is on, it obfuscates the list of outgoing changes that I need to push. Rating 0/10 |
Thank you for the link. After deactivating it, everything is working fine again. I don't understand why features like this are applied by default. It leads to a very bad user experience. |
Maybe they need more users testing the Insiders edition to yell early. |
Thanks again for all the feedback. In the latest VS Code Insiders release we have added multiple options to easily hide the history graph: 1) right click on any empty space in the "Source Control" view, and use the "Show Incoming/Outgoing Changes" action, We are also evaluating moving this information into a separate view. |
I'll be honest here. The most sensible change to do here is just make this not be enabled by default. People who have a small number of commits can turn it on if they so wish, and those who have a large number of commits won't immediately have their senses assaulted by it. |
Please make it a opt-in, this is definitely annoying enough that people sought how to disable it despite the fact that the user isn't being prompted for any preferences regarding this option. |
YES! |
Turn this off by default please. |
I also hate it. If I wanted to see a snakes nest, I wouldn't waste so much time managing cables on my desk. |
It loads 5 years of coding everytime i do something on git and commiting and pushing takes now painfully long. And it cant be turned off also. Very bad. Already looking from alternatives from competition. |
Thanks again all for your feedback. The history graph has been moved into its own dedicated view - Source Control Graph. The new view is still limited to the current/remote/base branches but next milestone we will be adding the capability to select any branches from the repository to be shown. The new view also uses caching, paging, and if the view is not visible or expanded no additional git calls are being made. The new view is already available in VS Code Insiders and will be included in the next VS Code Stable release. |
Thank the git lords you put this in its own view!! It was driving me nuts was about to force myself to switch to JetBrains or something. |
Even in its own view, for the life of me, I can't figure out what it's for. As far as I can tell, it's a different take on what we already have: the |
Or maybe I'm confused because I already use the graph functionality of https://marketplace.visualstudio.com/items?itemName=mhutchie.git-graph and I'm now realizing that this is is just the built-in version of that? |
Please don't dump such productivity disruptor on us again! |
Does this issue occur when all extensions are disabled?: Yes
Steps to Reproduce:
git status
shows "Your branch is up to date" and "nothing to commit, working tree clean"It used to show only the commits which really needed to be pushed or pulled.
The text was updated successfully, but these errors were encountered: