gistfile1.txt

@schrodincat I didn't notice you updated your message.

That's an off-topic discussion, but I recommend reading:
* [GitFlow considered harmful](https://www.endoflineblog.com/gitflow-considered-harmful) by Adam Ruka
* [What are the pros and cons of git-flow vs github-flow?](https://stackoverflow.com/q/18188492/802365)
* [Trunk Based Development](https://trunkbaseddevelopment.com/)

Personally I tend to a simple workflow: 
* a master branch that is functional/readable ; 
* short-lived pull requests (less code=better) ;
* continuous deployment/delivery.
* rebase strategy ;

This encourage:
* strong tests culture ;
* pair-programming (shorten feedback loop) ;
* code review (discussion and knowledge sharing) ;
* continuous integration (validation) ;