Programming

17351 readers

323 users here now

Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!

Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.

Hope you enjoy the instance!

Rules

Follow the programming.dev instance rules
Keep content related to programming in some way
If you're posting long videos try to add in some form of tldr for those who don't want to watch videos

Wormhole

Follow the wormhole through a path of communities !webdev@programming.dev

founded 1 year ago

MODERATORS

snowe@programming.dev

Ategon@programming.dev

MaungaHikoi@lemmy.nz

How large pull requests can exacerbate complexity and slow down development (graphite.dev)

submitted 11 months ago by morg@zorg.social to c/programming@programming.dev

10 comments fedilink hide all child comments

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

[–] Paradox@lemdro.id 10 points 11 months ago (1 children)

Graphite is ok, but honestly it's a solution in search of a problem

Maybe if you have a massive pr, splitting it up like this works, but that's really a planning failure. Stories should be smaller, and if you need to keep them separate for a long time, use feature branches

[–] oddityoverseer@lemmy.world 3 points 11 months ago (1 children)

Feature flags are another solution. Merge the code, but have it disabled on prod until you enable the feature flag (when the whole feature is complete and deployed)

[–] Paradox@lemdro.id 2 points 11 months ago

I've only ever worked in one codebase that didn't need feature flags, and even then we could have used them.