Ok I got the answer from IRC after a long chat. I’ll have to work with forks and pull requests, or add pre-push hooks on each dev’s machine since GitHub doesn’t allow per branch permissions neither pre-publish canceling hooks. Here is a part of the answers I got:
Fork the repository. then the developer can work on their own version of the repository, and doesn’t have to worry about committing to the wrong branch. And then someone upstream can always merge into whatever branch should be committed into.
Yeah but we’re a company and we don’t want that all our devs have forks
Why not?
Well they should be able to push their branch on a common repo to work with some other devs on the same feature for example.
Have a read through https://help.github.com/articles/using-pull-requests. You can still send patches around between multiple forks. This is the model that git was built on
I know but I want to be able to see quickly in a central way the actual work on any feature/hotfix, …
To cut a long story short: GitHub doesn’t support per-branch permissions