Whether youβre steering an open source project or leading full-time a software development team, the key to maximizing productivity lies in efficient code reviews.
I do almost exactly that workflow as well, but I just know its bitten me before. Protecting main/dev is fine, but I have also accidentally force pushed to the wrong branch and wiped out its work as well.
Muscle memory + Fatigue == Bad time :/
Yeah, or sprint to your colleague and ask them to force push their branch again :D
Another tactic for for getting clean git commits is to do all your messy commit work in a scratch branch, and then when your happy, create a new branch, and with meld, organise your changes into complete logical commits. We do that a little bit.
Pays to know how to recover code from the reflog in these cases.
At first I read that as re-flog. Is that with a cat oβ nine tails? π
