VS2019 change in newbranch also happens in master

Question

VS2019 change in newbranch also happens in master

Bill Pennock 1

steps: In Visual Studio Community 2019

Create a newbranch from Master
switch to newbranch using git changes view locals
make a code change to a file and save and close
git changes show the changes but I haven't staged them yet
switch to master same way
wait for the background task to complete
open up the file and it has the same changes I just made to newbranch

I don't get it?

Viorel 122.6K Reputation points

2023-01-03T22:06:30.423+00:00

I think that this is the expected behaviour. Your work is not lost when you change the branch in this manner. The new Visual Studio 2022 actually asks to keep or discard the changes.
Bill Pennock 1 Reputation point

2023-01-03T23:17:50.66+00:00

Further. I switched to VS2022 and when I attempted to change branches I got a message "bring the changes to master" or "stash the changes" or loose the changes. I thought the whole point of branches is you could quickly switch between code without changes and code with changes and the changes would stay in the branch and the master would remain unchanged. This "must stash" --feature-- just adds a layer of stuff to do that doesn't appear to serve a purpose. Can someone tell me either how to turn that off and go back to the git i know and love or why I should embrace this and it's a good thing?
Bill Pennock 1 Reputation point

2023-01-03T23:21:00.88+00:00

yes, there was no message in 2019 to that affect but I saw it in 2022. But see next comment, I that is not the behavior that I expect from Git. Can it be turned off? Why use branches at all, why not just stash.

1 answer

Your answer

Viorel 122.6K Reputation points

2023-01-03T22:06:30.423+00:00

I think that this is the expected behaviour. Your work is not lost when you change the branch in this manner. The new Visual Studio 2022 actually asks to keep or discard the changes.
Bill Pennock 1 Reputation point

2023-01-03T23:17:50.66+00:00

Further. I switched to VS2022 and when I attempted to change branches I got a message "bring the changes to master" or "stash the changes" or loose the changes. I thought the whole point of branches is you could quickly switch between code without changes and code with changes and the changes would stay in the branch and the master would remain unchanged. This "must stash" --feature-- just adds a layer of stuff to do that doesn't appear to serve a purpose. Can someone tell me either how to turn that off and go back to the git i know and love or why I should embrace this and it's a good thing?
Bill Pennock 1 Reputation point

2023-01-03T23:21:00.88+00:00

yes, there was no message in 2019 to that affect but I saw it in 2022. But see next comment, I that is not the behavior that I expect from Git. Can it be turned off? Why use branches at all, why not just stash.

Answer 1

Answering my own question after doing further testing. I noticed in the message that offered to move the changes to master that it said uncommitted changes. I am a full time project manager that was a programmer and still do some programming. So maybe my memory was wrong but I don't believe I had to commit changes in a branch in order for them to stay in the branch. But if I do commit the changes in newbranch I can then change back to an unchanged master. If anyone knows how to avoid this by some sort of option let me know.

Share via

VS2019 change in newbranch also happens in master

1 answer

Your answer