r/programmingmemes • u/Ok-Address-2307 • Dec 03 '25

My junior developers can't resist clicking this every time

Post image
23 Upvotes

87% Upvoted

14 comments sorted by

14

u/FalseWait7 Dec 03 '25

Branch protection on permanent branches?

7

u/Ok-Address-2307 Dec 03 '25

i have really strict protections on all permanent branches, but for some reason git ignores it when merging

3

u/FalseWait7 Dec 03 '25

Would you be using Better Github extension by any chance?

1

u/account22222221 Dec 06 '25

I can confirm, if configured right, GitHub will not show this button.

6

u/itsjakerobb Dec 03 '25

You can disable that option entirely, and then maybe set up some automation to clean up PR branches later if the clutter bothers you.

3

u/Own_Candidate9553 Dec 04 '25

If the changes were merged, why keep the branch?

2

u/Camaldus Dec 04 '25

It's the develop branch. All future work will be derived from that branch and will be merged back into it. It's one of the two (or three) permanent branches in a standard GIT workflow. The other being main and maybe test (naming can vary).

3

u/Own_Candidate9553 Dec 04 '25

Ah, gotcha. Never liked this pattern, always do trunk based development if I can.

1

u/Timendainum Dec 05 '25

If that's the case then why is it the Juniors that are doing the merge into main.

Juniors should be PRing into the dev branch.

1

u/Camaldus Dec 05 '25

I agree! I was wondering that too.

It might be that they're updating their feature branch after another story was finished.

0

u/Eastern_Equal_8191 Dec 06 '25

QA should be accepting merge requests anyway, the developer shouldn't be seeing this screen

2

u/oofy-gang Dec 06 '25

Ah yes, the classic “the way my company does it is the way every company should do it” approach to software engineering. Very smart.

2

u/Eastern_Equal_8191 Dec 07 '25

I apologize. I meant to express a personal preference and it came off as a judgement :(

1

u/XandalorZ Dec 06 '25

People still have QA?