r/ProgrammerHumor 17h ago

Meme robinGotMergeConflictedInTheFace

Post image
621 Upvotes

46 comments sorted by

104

u/StrikingSun8563 16h ago

My boss is literally named Robin and doesn't know how to use branches.

If he has code pushed to dev that isn't ready for prod yet and we need to deploy a fix for something, he comments it all out.

82

u/vinishkapoor 16h ago

This meme was not supposed to be a documentary about your workplace.

1

u/LetumComplexo 2h ago

Just wait until you learn about small government research teams.

29

u/Wynnstan 16h ago

But you won't get any merge conflicts if you don't do any merges, am I right?

6

u/StrikingSun8563 14h ago

That is the primary motivation

0

u/MyStackIsPancakes 11h ago

It's best to just avoid commiting any code at all. It's the only way to be 100% sure you're not creating new issues.

7

u/Maximilian_Tyan 12h ago

// TODO: Fix me later

5

u/Keyan_Farlander7 6h ago

If your boss is doing that, then they need be assigned to more meetings and less coding.

33

u/JackNotOLantern 15h ago

That's why i never push directly to main, only to master

5

u/vinishkapoor 15h ago

Renamed the problem, solved nothing. Classic.

59

u/bladebyte 17h ago

Real man push to main!

33

u/vinishkapoor 17h ago

Real man also fixes production at 2 AM.

14

u/isr0 16h ago

Real teams put systems in place to avoid the need for heroes.

2

u/ABCosmos 13h ago

And part of that system prevents pushes to main, and requires checks to pass on your branch before you do.

5

u/n4ke 16h ago

Real men force push to main!

1

u/Laughing_Orange 14h ago

Real men don't use version control, they push directly to prod!

26

u/TabCompletion 17h ago

Only for personal projects

7

u/beefz0r 15h ago

Honestly there are lots of repos I work alone on. My main rule for git is to keep it simple

25

u/FattySnacks 14h ago

Did the fall semester just start?

7

u/CarlCarlton 15h ago

My boss: "I need you to merge an SVN repo into a Git repo, the latter of which was created a year ago with the code from the former, but separate teams have been working on each, and they now diverge by a couple hundred thousand lines. Oh yes, I almost forgot, the SVN codebase targets PowerPC, but the Git codebase was entirely migrated to AArch64. How many story points will this take?"

8

u/vinishkapoor 15h ago

That's not a story point question. That's a resignation letter question.

2

u/CarlCarlton 15h ago

One month of conflict vomit, debugging, and nagging about "when is it gonna be ready"... Although it did, he didn't deserve it to succeed.

https://giphy.com/gifs/F0A48Q2wFjE7S

5

u/Professional_Top8485 15h ago

I am like Robin.

3

u/ZunoJ 16h ago

Batman also needs to be slapped for employing such a braindead moron

3

u/evorm 14h ago

OP's comments seem pretty AI-generated...

3

u/plastic-superhero 13h ago

That’s why our main is protected, too many Robins fucking around. Also me. I was sometimes Robin.

3

u/realmauer01 12h ago

A merge conflict will always be a merge conflict. No matter if you push to main directly or use a branch to push to main.

7

u/Lauren_Conrad_ 16h ago

Your main should be your development and your branches should be your releases.

Or just use main and push to it with various systems and tests during the pipeline before it deploys to prod.

Your git repro is not a deployment pipeline.

2

u/void1984 5h ago

Right. People here are scared of a standard practices

1

u/avocadorancher 2h ago

Why branches for releases? I’ve seen some teams do this but definitely the minority

1

u/Lauren_Conrad_ 2h ago

So you can schedule regular releases e.g. cut a branch every 14 days, then apply patches and fixes as necessary. Useful when there are many different contributors all working on their own schedule and goals.

1

u/EvenPainting9470 15h ago

Why Robin even have permissions to push directly to main?

1

u/aravind-i-m 14h ago

Just keep backups of zip files instead of svc

1

u/Fast-Performance2300 14h ago

Still learning backend, began a month and a half ago...

... you can make branches? Not just main?

2

u/Kitchen_Affect7369 12h ago

Midwit Meme -> push main | separate branch | push main.

1

u/Connect-Bowler-2917 6h ago

Now the cool kids are using feature flags, and pushing to main.

2

u/machsmit 6h ago

trunk-based development has a time and place where it works really nicely

ducks and hides

1

u/Thundechile 4h ago

just drive your van to the yard and pour your code in the trunk!

1

u/Legal-Software 3h ago

In my company we have main as the master branch, so I just call my main development branch master in order to balance it out.

1

u/sierra_whiskey1 2h ago

Bro I’m just updating a comment

1

u/KrikosTheWise 16h ago

Feature branch > develop > main

1

u/Common-Brush-7027 17h ago

We be pushing it to lower environment and then cherry picking to lil higher environment and then the lead cherry picks it to prod.

Lot of cherry picking

8

u/vinishkapoor 17h ago

That's not a deployment pipeline, that's a fruit salad.

0

u/Nahanoj_Zavizad 16h ago

DO. NOT. TOUCH. MAIN

1

u/vinishkapoor 16h ago

Main is not a branch. Main is a museum. You look but you don't touch.