I usually spend a lot of time writing thoughtful answers but since I'm in bed and your question is IMHO very easily googlable here are a few things to check out

I usually spend a lot of time writing thoughtful answers but since I'm in bed and your question is IMHO very easily googlable here are a few things to check out: - Gitlab flow: a variation of the Git flow system optimized for Github - Git flow: what the former is based off of - the search terms "git workflow" or "git branching model" - my two cents: your workflow depends on your team and project structure. For a single person project I commit to master and push to the remote. For a two person side project I'd recommend the same only we both push to remote master. If the team gets bigger I'd do pull requests to master. If it's a client project I deploy master to staging and version tags to production. - branches are cheap, use them to isolate small units of work, or don't if it's your personal project. But even then I run tricky experiments in branches and discard them if the fail