Ooh thanks for identifying that only the local is deleted.
So this was my thought process: I thought they were pulling from a forked repo. I also thought they meant checkout master as my-new-branch, delete master locally AND remotely, and push my-new-branch as the authoritative new master
It seems weird not to keep previous work around for future reference. I suppose they wanted to reduce redundancy of branches or repo files at that point. My mind likes to makeup stories
The work is always there in the.git folder. You just don't have the "branch".
But once you do git checkout -b my-new-branch origin/master, you'll have an identical copy of origib/master it'll just be called my-new-branch locally.
git checkout -b my-new-branch origin/master
So when you build your future with, it's built it the latest files.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.