89

I've heard it thrown around in professional circles and how everybody's doing it wrong, so.. who actually does use it?

For smaller teams

"scaled" trunk based development

you are viewing a single comment's thread
view the rest of the comments
[-] jjjalljs@ttrpg.network 12 points 5 months ago

Here there's main. You branch off. Do your work. Make a PR to main. Build passes and someone approves, merge to main. Production release is done by tagging main.

The branches are short lived because the units of work we select are small. You have like one pr for an endpoint. You don't wait until the entire feature with 20 endpoints is ready to merge.

Seems to work fine. I think this is different than trunk based development but honestly I'm not sure I understand trunk.

[-] mundane@feddit.nu 1 points 5 months ago

This is enough for most projects.

[-] onlinepersona@programming.dev 1 points 5 months ago

Seems to work fine. I think this is different than trunk based development but honestly I’m not sure I understand trunk.

Same. But it feels like you're doing it.

Anti Commercial-AI license

this post was submitted on 15 May 2024
89 points (95.9% liked)

Programming

17314 readers
238 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

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