How it works...
Okay, so it's not really magic, just the product of some extremely brilliant coding.
When we branched from master (or any branch, for that matter), we created a point-in-time clone of that branch in our new one. We then made changes to the branch, doing things like testing configuration changes, or purposefully breaking things, without affecting the master branch (and our known good configuration).
That much is easy to understand (I think), but the problems begin when we want to make sure that our changes are pushed to the server.
We ran git push, which complained. This was because we didn't have a section in our .git/config file that told git where to push our local branch.
After we run the suggested command, our .git/config ...
Become an O’Reilly member and get unlimited access to this title plus top books and audiobooks from O’Reilly and nearly 200 top publishers, thousands of courses curated by job role, 150+ live events each month,
and much more.
Read now
Unlock full access