BenLloydPearson@programming.dev to Programming@programming.devEnglish · 1 year agoWhy I prefer trunk-based development - Trisha Geetrishagee.comexternal-linkmessage-square22fedilinkarrow-up139arrow-down13cross-posted to: technews@radiation.party
arrow-up136arrow-down1external-linkWhy I prefer trunk-based development - Trisha Geetrishagee.comBenLloydPearson@programming.dev to Programming@programming.devEnglish · 1 year agomessage-square22fedilinkcross-posted to: technews@radiation.party
minus-squarejpfreely@programming.devlinkfedilinkEnglisharrow-up8·1 year agoMy understanding of trunk based development is that it allows for short lived branches and keeps longer work behind feature flags as it is merged in pieces. The common CI approach with pull/merge requests having to pass tests still applies.
minus-squareJackbyDev@programming.devlinkfedilinkEnglisharrow-up3·1 year agoThat isn’t what the author describes, but I agree there are multiple interpretations.
My understanding of trunk based development is that it allows for short lived branches and keeps longer work behind feature flags as it is merged in pieces. The common CI approach with pull/merge requests having to pass tests still applies.
That isn’t what the author describes, but I agree there are multiple interpretations.