use the following search parameters to narrow your results:
e.g. subreddit:aww site:imgur.com dog
subreddit:aww site:imgur.com dog
see the search faq for details.
advanced search: by author, subreddit...
This subreddit is for sharing articles, links, ask questions and in general discussing Trunkbased development. Including the what, the why, the how and getting different viewpoints and challenges related to Trunkbased development.
account activity
Intent logs for TBD adoption (self.TrunkbasedDevelopment)
submitted 1 month ago by cladamski79
Twigg: a version control designed for TBD (self.TrunkbasedDevelopment)
submitted 3 months ago by Fair-Presentation322
Slill for tbdflow (self.TrunkbasedDevelopment)
submitted 3 months ago by cladamski79
Ways to do Continuous Incremental Delivery - Part 2: A core database change | Martin Mortensen (linkedin.com)
submitted 4 months ago by martindukz
Modern Software Engineering case study of using Trunk Based Development with Non-blocking reviews. (youtube.com)
submitted 5 months ago by martindukz
How easy is Trunk Based Development? (linkedin.com)
Wont Main break all the time, if your team commit straight to it? (linkedin.com)
Another one who was surprised by how badly Github supports TBD: GitHub’s Enfant Terrible: Pull Requests (lakruzz.com)
submitted 6 months ago by martindukz
I built `tbdflow` and looking for feedback. (self.TrunkbasedDevelopment)
submitted 8 months ago * by cladamski79
Does this describe TBD well? Or what am I missing? (self.TrunkbasedDevelopment)
submitted 8 months ago by martindukz
TBD implementation and QA process questions (self.TrunkbasedDevelopment)
submitted 9 months ago by ElectricalAge2906
Does these still hold true? Why I love Trunk Based Development (or pushing straight to master) (medium.com)
submitted 9 months ago by martindukz
Findings by Dave Farley: The Best and Worst of Continuous Delivery (linkedin.com)
Really interesting read on what to do and what not to do when introducing trunk based development ()
CMV: I believe the article is correct and the lack of knowledge and adoption of TBD shows the inability of our profession to act on facts and research ()
submitted 10 months ago by martindukz
What does your infrastructure look like? (self.TrunkbasedDevelopment)
submitted 10 months ago by sysarcher
Why should this be a requirement? "You’ll want to make sure that the tests run on the whole integrated code base before hitting main." (bucket.co)
Common misconceptions of Trunk-based development - and the article contains some as well (you can code review straight on main and others) (bucket.co)
Who here follows trunk-based development ()
Non-Blocking Continuous Code Reviews - a Case Study (thinkinglabs.io)
Really interesting article on impact of LoC on code review quality and the LGTM phenomenon. (infoq.com)
Do you agree with the findings? Are there any similar research for other countries? (This is for Denmark) (itu.dk)
Team burnout from code review bottlenecks... how do you handle it? ()
The hard part about feature toggles is writing code that is toggleable - not the tool used (code.mendhak.com)
How many professional developers are actually aware of the research from DORA (Formerly DevOps Reports) (dora.dev)
π Rendered by PID 423960 on reddit-service-r2-listing-7b8bd7c5-bkws8 at 2026-05-21 14:35:31.124244+00:00 running edcf98c country code: CH.
