We are using features branch that we are rebasing on master. This allow to have code reviews before something is actually in master (something you might or mig

We are using features branch that we are rebasing on master. This allow to have code reviews before something is actually in master (something you might or might not want depending on your worflow or criticity of the sw you are working on) Rebasing (and squashing) allow to keep a linear and clean history. Rebasing and squashing also have downsides, you lose the finer day to day commits, in exchange of ideal history, but at least it should be mentioned in a 2019 post about having too much feature branches in git...