The new editor has a much more refined way to work with branches in the git repository than the old editor.
Here is an use case that was not the reason why it has been designed as it was, but you can do it and it just saved me some time and helped me not playing with fire. Hence I think it qualifies as a sneaky new feature.
I was working on the dev branch, modifying many forms and modules and didn’t want to merge to prod because I would have very likely broken the production app.
I also did a little and safe change to an http endpoint. The new endpoint was compatible with the production app, but was in dev, so I couldn’t test it because it was called by another application that I didn’t want to modify.
So I copied the http endpoint code, set the current branch to prod, pasted the code, set the current branch back to dev, and now I had the new http endpoint working in the old production app, without needing any merge or modifying the 3rd application that was calling the http endpoint or doing anything crazy like I used to do.