If you don’t know how to branch your repository into different branches and if you mess up while merging your changes,your codebase will end up as a complete mess.
So get your notebook out, we are going to learn how to do these things in vs code without the terminal. I’m also going to give you some practical tips so you can be confident when working on your new project.

This video is part 5 of a series about GitHub and vs code.
Today I’m going to show you how to securely add a feature to your project with merge and branch, so your main project can keep going while you secretly work on the new great feature. I’m also going to show you the best way to then implement those changes seamlessly.

There are two main things we have to understand.
First of all, there are two systems running with our file changes, the local system and the “Cloud System” or we could also say the GitHub system. In a perfect world, these would be synched all the time, but we are responsible for keeping those systems synched.

The other thing is, that we are able to have not just one code base running but multiple… in branches.

Here for example we have a website for our company where we want to change something. The change should not affect the current website until we are sure all our changes work. So we want a main or correctly said “master branch” and we want our changes on a working branch which we merge together once we are sure the changes are the way we want them to be.

#github #vscode #developer #programming

How To Use GitHub with VS Code in 2020 | Merge, Branch & Pull Request
1.70 GEEK