Hey, Jan, I understand your point, merging can cause some frustration, especially when conflicts happen.
Kolosek team prefers to create a new branch for each feature unless it is a hotfix or emergency bug fix. In this case, we commit directly to master or development.
To ensure the code is "clean" we always have someone to check the Pull Request before merging the feature branches. This is another reason why we mostly go with feature branches.
We're a place where coders share, stay up-to-date and grow their careers.
We strive for transparency and don't collect excess data.