Oddbean new post about | logout
 You can avoid confusion by making a develop branch which can break, and put in master only things you know that are working well 
 We have these branches:

`master` branch - intended to never be rewritten, all schema changes will only go forwards, safe for general use
`unstable` branch - intended for developers and enthusiasts who want to help test new code, might require database wipes. Might be force pushed (rewritten, not cleanly 'pull'able).
Topic branches - intended for developers only, often just the one developer working on that topic. Totally unsafe, may break databases, tends to get force pushed and rebased onto unstable.