Trunk Based Development
trunkbaseddevelopment.com
A portal on this practice

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

  • Consti
    10•1 month ago

    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.

      • Consti
        5•1 month ago

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

          • Consti
            1•1 month 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