https://python.coderdojohasselt.be/en/sessions/git/12-git-branches/index.htmlLast session you learned to make commits: snapshots of your code on one timeline. Everything neatly one after the other. But what if you want to try out a new idea? Adding a laser gun to your game, for example. You don’t know whether it will work. You don’t want to break your working code. That is what branches are for. A branch is a copy of your code where you can experiment freely. Your main code (the master branch) stays safe. If your experiment works, you paste it back into master. Doesn’t it work? You throw the branch away. Your master branch never noticed a thing.Hugoenhttps://python.coderdojohasselt.be/en/sessions/git/12-git-branches/mentor-notes/index.htmlMon, 01 Jan 0001 00:00:00 +0000https://python.coderdojohasselt.be/en/sessions/git/12-git-branches/mentor-notes/index.htmlGoal of this session At the end of this session a ninja can: Explain what a branch is and why you would use one. Create a branch (git branch / git switch -c), switch to it, and back to master. Make commits on a branch without affecting master. Merge a branch into master with git merge. Recognise and solve a simple merge conflict. Delete a superfluous branch with git branch -d. What is not expected: remote branches, pull requests, GitHub integration. Those come in sessions 13 to 15.