Git Local Changes grouped by project name?

Answered

I have once opened a project and selection option 'Attached', removed since, but I believe since then in Git - Local Changes I see any changes grouped by the project name. How can I get rid of that line? It seems superflous and I really don't need it.

1
6 comments

Hello Benomatis

You can manage "Grouping" under the button that can be found in the navigation bar (in your case it's on the left side of Local changes tab)

1

Thanks, Ruslan Kuleshov, but I only have 'Directory' there and choosing it will just group the changed files by directory showing the full path from the root of my system, that line with the project name will remain above it, as if it was some sort of higher level grouping.

So it's apparently not a module, and not a directory either, but what is it then...? It also has this dark red square in front and if I hover over it, the tool tip that appears will say 'No tracking branch'.

0

Benomatis thank you for the clarification.
The red square can come from 3rd party plugin.

Speaking of a grouping issue, it seems that you have faced a bug reported here:
https://youtrack.jetbrains.com/issue/IDEA-263091

As a workaround you can try to:
1. Attach a new module
2. go to Preferences | Version Control and make sure that there are 2 VCS roots listed. 
3. go to Local changes and disable grouping by Module
4. Remove freshly added module and check Preferences | Version Control

1

Thanks so much Ruslan Kuleshov that fixed it, except Local Changes is not grouped by Module but by Repository, unchecking it in 'Group by' did the trick!

The linked issue says 'Fixed' - how can I find out where it's fixed? Is it in a recent version or has it just been established that this is expected and can only be solved using the above workaround? I'd expect the grouping to simply disappear (get deactivated) if the module is removed, but it might just be me.

0

Benomatis I am really happy to hear that the issue is resolved now.

We've found this issue in the current version and the developer has already fixed it.
In the future release grouping will be disabled once there is only one VCS root in the project.

1

Please sign in to leave a comment.