4 ms·
I agree, communication is essential. The most important thing is that the developers agree on how they work with git, and all these branching models are just us
by mcv 11y ago
I agree, communication is essential. The most important thing is that the developers agree on how they work with git, and all these branching models are just usable defaults and starting-off points from which you figure out what works for your organization.
But preventing the new guy from pushing straight to master is not that hard. On my current project, a git hook prevents merging commits into the remote master if that commit doesn't already exist in another remote branch. So you have to do your work elsewhere or it won't be accepted.
- Gratsby 11y agoUnless of course he sees an error and runs `git push --no-verify`. I'm not really saying any of the advice around git workflow is bad. It's that too much time spent on process instead of development is. If you take the advice for what it is - a good starting point - I think it's great to use.
- mcv 11y ago> Unless of course he sees an error and runs `git push --no-verify`. Yes, but then you know he's someone you need to fire. That's also useful knowledge.