this post was submitted on 04 Apr 2024
1113 points (98.1% liked)

Programmer Humor

19512 readers
418 users here now

Welcome to Programmer Humor!

This is a place where you can post jokes, memes, humor, etc. related to programming!

For sharing awful code theres also Programming Horror.

Rules

founded 1 year ago
MODERATORS
 
you are viewing a single comment's thread
view the rest of the comments
[–] [email protected] 51 points 7 months ago* (last edited 7 months ago) (26 children)

I prefer to rebase as well. But when you're working with a team of amateurs who don't know how to use a VCS properly and never update their branc with the parent branch, you end up with lots of conflicts.

I find that for managing conflicts, rebase is very difficult as you have to resolve conflicts for every commit. You can either use rerere to repeat the conflict resolution automatically, or you can squash everything. But when you're dealing with a team of Git-illiterate developers (which is VERY often the case) you can either spend the time to educate them and still risk having problems because they don't give a shit, or you can just do a regular merge and go on with your life.

Those are my two cents, speaking from experience.

[–] [email protected] 9 points 7 months ago (4 children)

How others are keeping their branches up to date is their problem. If you use Gitlab you can set up squash policy for merge requests. All the abomination they’ve caused in their branch will turn into one nice commit to the main branch.

[–] [email protected] 13 points 7 months ago (2 children)

In a small team at a small company it becomes my problem pretty quickly, since I'm the only one that actually has some clue about what git does.

[–] [email protected] 6 points 7 months ago

This. When they get any sort of conflicts in their pull request, it becomes MY problem because they don't know what to do.

[–] [email protected] 2 points 7 months ago

Heaven forbid my teammates read any documentation or make any attempt to understand the tooling necessary to do their job.

That being said, I taught my dumbass git-illiterate team members a rebase workflow, with the help of the git UI in Pycharm. Haven't had any issues with merge conflicts yet, but that might just be because they're too scared to ask me for help any more

load more comments (1 replies)
load more comments (22 replies)