Version control local changes tab missing in 2020.1

EDIT: the same functionality is available in the Commit pane, which can be accessed (on MacOS) via command+0.  I'm on 2025.1 and this issue is no longer relevant and should be closed as Resolved.

As you can see in the screenshot below (2025.1), this contains the Rollback option, the local changes, and all other functionality that people in this thread have mentioned.

Hello! It's was much more convenient with that changes tab. If you are able to revert it back - please. As people say - it was perfect :)

I also wanted to find that local changes tab, because there was a reference to it somewhere in the manuals.

As I got it, now you can check and revert all uncommited changes here.

So, can't see any problem

It's 2023 outside and after today's update, local changes suddenly disappeared. Thanks to this thread was able to get it back. Thanks for posting the answer

Just hope the will not remove it in future

Is the “Use non-modal commit interface” still working in 2023.3.1?

I just updated and it seems that the Local changes tab is gone again. (Or is there some other problem with my Git repositories?)

I was updated to version 2023.3.2 by snap and now I cannot find the Local changes tab anymore, what is wrong with these people 

Hey Jetbrains team. It has been almost 4 years now. This is absolutely ridiculous. When will you revert this change?

It seems that the old interface is gone for good in version 2025.1 — at least, I couldn’t find a way to enable it. At first, I was pretty frustrated, but after investing just 10 minutes in getting to know the new interface (the "Commit" window), I found that it's actually better than the old one.

I'm not trying to convince anyone here — just suggesting you give it 10 minutes and try the new interface out. Personally, I couldn’t find any use cases that weren’t covered in the new one.

Sergei They unfortunately will not do that. No one from the team has commented on this thread in 5 years now. They made a ridiculous change and won't even try to defend it. 

They did remove it in the latest PyCharm (2025.1). 

I've calculated that losing access to the local version will cost me 2 days of productivity per work year. This isn't just my issue—I recently held a meeting where our team of 10 developers confirmed this is a definitive problem for them too, meaning we're looking at a total loss of 20 workdays annually. I'll therefore dedicate 2 more days to learning Visual Code, and if I can master it and find its Git interface superior to PyCharm's, I'll formally request our manager to discontinue PyCharm licenses and will train our entire team on Visual Code instead.

Sergei  you said:

After investing just 10 minutes in getting to know the new interface (the "Commit" window), I found that it's actually better than the old one.

Can you explain in detail what the advantages and disadvantages of the new interface are, because many people—including myself—don't understand it.

:(

Guys, if you work in the software industry you've been in these meetings.  You've been part of this situation.  They made their decision, they planned it, they implemented it, they shipped it.  Move on.  It's been years at this point.

Software moves forward, things change, you adapt.  That's not new and shouldn't be unexpected.  I feel for you, I felt the same way in 2023.  But if you're losing significant time it's because you're deciding not to learn how to use the new tools, not because the new tools are inherently slower.  Jetbrains is almost certainly not making design decisions just to piss you off and waste your time.

 VS Code is definitely a great editor and I use it any time I need to open a random file.  But as someone who knows and uses both VS Code & Jetbrains suite of products, I'd certainly give it more than 2 days before you start cancelling any licenses.  

I think it is a time to start the migration from this IDE.
If this is the way they make software, they won't have my money (and I'll ask my company to get rid of my license as well). So, no money from my side to stupid jetbrains.

That is rude and uncalled for.  Do you appreciate it when customers talk to you like that at work?  You paid for a license to use the software, not a license to insult them personally.  I swear, the entitlement these days.

Furthermore, the new Commit panel contains all of the functionality of the old Local Changes panel.  To show the local changes you press cmd+0 now rather than cmd+9.  It's on the left side of the screen rather than the bottom.  It didn't take me long to figure out.  I am on 2025.1 and all of the functionality I have ever used is there and working.  Are you complaining that the button moved?  Or that you couldn't find the button?  

This topic is about the Local Changes panel.  Since the new Commit panel now contains that functionality, this topic should likely be closed.  If you are complaining about something else, you will need to give people a clue about what it is, and I'd file a new topic for that.

Can you explain in detail what the advantages and disadvantages of the new interface are, because many people—including myself—don't understand it.

Have you considered asking ChatGPT?  That might save you time in the future.  

From my perspective of having explored this for barely a few minutes, it looks like the benefits would be a cleaner separation between uncommitted changes and the repository state.  As you probably know, uncommitted changes are not part of the repository.  All of the related functionality is under the Commit pane (cmd+0).  For the repository state, that functionality is under the Git pane (cmd+9).  Whereas before uncommitted changes were in the Git pane, while the rest of the stuff that is now in the Commit pane was somewhere else.

To me that is a relatively minor but meaningful improvement.  Browsing repository state and checking out branches is fundamentally a different part of the workflow than making a new commit.  Again, if you get confused I would consider reading the documentation, asking ChatGPT, or asking someone on a forum.  My gut feeling says that will be more successful than threatening to cancel your subscription because a button moved.  Now I am going to figure out how to unsubscribe myself from this thread.

Brandon Fryslie Signup It's not complicated to understand that they separated the window between git (Alt-9) and commit (Alt-0 as a keyboard shortcut - I'm specifying this in case you think I haven't done my own research).

I've personally purchased the JetBrains suite for more than 10 years, I understand their design philosophy perfectly, and I convinced my company (where I've been employed for 5 years) to purchase all JetBrains licenses. I've been working with Rider for nearly 10 years (I developed a game in Unity), GoLand, and I use PyCharm daily. I don't think I'm a fool who can't understand the difference between two window systems.

I've always encouraged changes that make me more productive, which is why I committed to JetBrains. This is simply a "change for change's sake" and nothing more. This type of change reminds me of when Windows centered their menu, showing they were incapable of major innovations and wanted to copy Apple (though I've always disliked that brand, having witnessed Apple's entire history and ethics, and have never touched an iPhone my entire life, God forbid!).

And thank you for suggesting ChatGPT... I won't comment on that. I'll just try to be constructive: indeed, the community has been complaining for years, and it only takes a few Planck seconds on Google to see what people have been saying on forums about this issue for several years. A large portion of users can't stand this new interface. That's not difficult to understand either. It's not complicated to conduct surveys and gather feedback on ergonomics improvements. We can see all the time spent trying to get user feedback, yet apparently not once have they asked questions about the interface or ergonomics - they don't involve users in this aspect at all. They probably think they're the best, but that's no longer the case. Yes, they were once the best, but with what they're doing now, that's no longer true.

NB: I've been following the JetBrains team closely for years, and apparently I was one of the few who knew they were the ones who invented Kotlin. Unfortunately, I have the impression that as soon as a developer becomes even slightly good, their ego inflates and they believe they're superior to everyone else. I don't consider myself a good developer, so I can allow myself to say whatever I want (lol), but I sincerely hope you're not that kind of people, when you ask someone you dont know to use ChatGPT.