News for hackers. Stuff that matters.
Re:Ask HN: Best Git workflow for small teams by a_alakkad on Sunday November 13, 2016 @01:39AM (#12942175)
We work as small team, 3-5 people max.

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?).

Re:Ask HN: Best Git workflow for small teams by perlgeek on Sunday November 13, 2016 @02:10AM (#12942226)
> 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.

Re:Ask HN: Best Git workflow for small teams by w4tson on Sunday November 13, 2016 @03:18AM (#12942401)
Couldn't agree more with this. There's a lot of cargo culting with fit.

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 ?