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 thread.
View all comments View context
-1 points
*

Commits are always up-to-date

Is this with git or svn?

Anti Commercial-AI license

permalink
report
parent
reply
5 points

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

permalink
report
parent
reply
2 points

Wait, you push to main directly? That’s not exactly what “trunk based” means.

permalink
report
parent
reply
1 point

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

permalink
report
parent
reply

Programming

!programming@programming.dev

Create post

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



Community stats

  • 3.1K

    Monthly active users

  • 1.8K

    Posts

  • 30K

    Comments