I’m kinda planning on teaching my team how to use interactive rebases to clean the history before a merge request.
The first thing they’ll learn is to make a temporary second branch so they can just toss their borked one if they screw up. I’m not going to deal with their git issues for them.
I disagree. I don’t wanna deal with my coworkers work, so I’m teaching them to deal with it themselves. Not necessarily in the best way for them to do it, but in an easy way to teach and an easy way to get right
I have been that friend from the alt text at every place I have worked. I shudder to think how they’re going about their projects without me, now.
I’m kinda planning on teaching my team how to use interactive rebases to clean the history before a merge request.
The first thing they’ll learn is to make a temporary second branch so they can just toss their borked one if they screw up. I’m not going to deal with their git issues for them.
These two statements contradict each other.
That’s why I’ll make damn sure they’ll make that second branch first.
Mind you, the most likely result is that I’ll still see branches with 50+ commits with meaningless names because nobody ever rebases anything.
I disagree. I don’t wanna deal with my coworkers work, so I’m teaching them to deal with it themselves. Not necessarily in the best way for them to do it, but in an easy way to teach and an easy way to get right