this post was submitted on 03 Mar 2024

1096 points (97.8% liked)

Programmer Humor

19602 readers

969 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

Keep content in english
No advertisements
Posts must be related to programming or programmer topics

founded 1 year ago

MODERATORS

Feyter@programming.dev

anzo@programming.dev

BurningTurtle@programming.dev

pylapp@programming.dev

1096

My Git Knowledge (lemm.ee)

submitted 8 months ago by sag@lemm.ee to c/programmer_humor@programming.dev

178 comments fedilink hide all child comments

you are viewing a single comment's thread
view the rest of the comments

[–] korok@possumpat.io 2 points 8 months ago (2 children)

Do you not use a fork as your origin, separate from the production upstream repo? I’ll push to my fork’s main branch for small or urgent changes that will definitely be merged before anything else I’m working on.

[–] Solemn@lemmy.dbzer0.com 1 points 8 months ago

If it's a private repo I don't worry too much about forking. Ideally branches should be getting cleaned up as they get merged anyway. I don't see a great advantage in every developer having a fork rather than just having feature/bug branches that PR for merging to main, and honestly it makes it a bit painful to cherry-pick patches from other dev branches.