We just keep it simple like:
- No one pushes to master.
- For every feature (or update on a feature), create new branch.
- Send pull request for reviewing (one of us is the reviewer).
- Merge pull request into master.
---
You could try git workflow, but it's just too complicated for small team (and for large teams too?).
git flow seems overkill, unless you regularly need to patch older versions. For software where you control which version(s) are deployed, you can usually get away with (much) simpler workflows.
There isn't one size fits all, different teams develop at different rates because of ability, requirements, deadlines, culture.
Just keep it simple stupid! Why have a separate branch for tags? Or hot fixes even ?