• Jim@programming.dev
    link
    fedilink
    English
    arrow-up
    6
    ·
    1 year ago

    Precisely. In practice, trunk based development just means your branch is local instead of on remote.

      • Jim@programming.dev
        link
        fedilink
        English
        arrow-up
        2
        ·
        1 year ago

        If the work I’m doing is on a feature branch on remote or locally, why does it matter to the rest of the team? My integration steps can be done on a server instead of locally. TBD forces teams to collaborate synchronously since changes are pushed straight to trunk. Rebase or squashes are irrelevant here.

        Another poster put it great: TBD is trying to solve a culture problem. Feature branches and pull requests into main is much more flexible. The only time TBD make sense is for small teams - like 2 or maybe 3. And even at 2, I’d much rather create feature branches that merge into main.