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

Programming

17488 readers
110 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 [email protected]



founded 1 year ago
MODERATORS
 

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
[–] [email protected] 10 points 6 months ago (1 children)

We do, for two 2-3 person projects, where no code reviews are done. This is mostly because (a) it's "just" a rewrite and (b) most new functionality is small and well-defined. For bigger features a local branch is checked out and then merged back later. Commits are always up-to-date, which makes it much easier to test integration of new featues.

[–] onlinepersona -1 points 6 months ago* (last edited 6 months ago) (1 children)

Commits are always up-to-date

Is this with git or svn?

Anti Commercial-AI license

[–] [email protected] 5 points 6 months ago (1 children)

With git. Every time we start work, we pull. After every commit, we push (and pull/merge/rebase) if necessary.

[–] [email protected] 2 points 6 months ago (1 children)

Wait, you push to main directly? That's not exactly what "trunk based" means.

[–] [email protected] 1 points 6 months ago

streaming small commits straight into the trunk

The image even calls it like that

Some things don't have good CI/tests, so it doesn't make sense to include the build step, especially on a small team where we trust each other. But yes, it's not good practice, and we don't do this on every project, but sometimes it's necessary to adjust the flow to the specific project