r/trunkbaseddevelopment

  1. 4points

    Twigg - a version control and software forge made for trunk based dev (self.TrunkbasedDevelopment)

    1 comments

  2. 1points

    Does a CLI like tbdflow need a GUI? (self.TrunkbasedDevelopment)

    0 comments

  3. 1points

    Interactive simulator: GitHub Flow vs trunk-based development - watch where work queues up (mainline.dev)

    0 comments · source

  4. 2points

    Intent logs for TBD adoption (self.TrunkbasedDevelopment)

    2 comments

  5. 3points

    Twigg: a version control designed for TBD (self.TrunkbasedDevelopment)

    4 comments

  6. 3points

    Slill for tbdflow (self.TrunkbasedDevelopment)

    3 comments

  7. 3points

    Ways to do Continuous Incremental Delivery - Part 2: A core database change | Martin Mortensen (linkedin.com)

    0 comments · source

  8. 5points

    Modern Software Engineering case study of using Trunk Based Development with Non-blocking reviews. (youtube.com)

    0 comments · source

  9. 1points

    How easy is Trunk Based Development? (linkedin.com)

    0 comments · source

  10. 3points

    Wont Main break all the time, if your team commit straight to it? (linkedin.com)

    2 comments · source

  11. 2points

    Another one who was surprised by how badly Github supports TBD: GitHub’s Enfant Terrible: Pull Requests (lakruzz.com)

    0 comments · source

  12. 6points

    I built `tbdflow` and looking for feedback. (self.TrunkbasedDevelopment)

    2 comments

  13. 1points

    Does this describe TBD well? Or what am I missing? (self.TrunkbasedDevelopment)

    2 comments

  14. 1points

    TBD implementation and QA process questions (self.TrunkbasedDevelopment)

    14 comments

  15. 3points

    Does these still hold true? Why I love Trunk Based Development (or pushing straight to master) (medium.com)

    0 comments · source

  16. 6points

    Findings by Dave Farley: The Best and Worst of Continuous Delivery (linkedin.com)

    0 comments · source

  17. 2points

    Really interesting read on what to do and what not to do when introducing trunk based development

    1 comments · source

  18. 1points

    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

    0 comments · source

  19. 2points

    What does your infrastructure look like? (self.TrunkbasedDevelopment)

    0 comments

  20. 1points

    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)

    2 comments · source

  21. 3points

    Who here follows trunk-based development

    2 comments · source

  22. 1points

    Common misconceptions of Trunk-based development - and the article contains some as well (you can code review straight on main and others) (bucket.co)

    0 comments · source

  23. 1points

    Non-Blocking Continuous Code Reviews - a Case Study (thinkinglabs.io)

    0 comments · source

  24. 5points

    Really interesting article on impact of LoC on code review quality and the LGTM phenomenon. (infoq.com)

    0 comments · source

  25. 6points

    Do you agree with the findings? Are there any similar research for other countries? (This is for Denmark) (itu.dk)

    4 comments · source