Code Review & Git Flow

Branch strategies, PR hygiene, merge queues, and trunk-based development.

  • 2 Tracked terms
  • Last 30 days Feed window

What this topic collects on

An article joins this feed when it matches these terms. Each one is also a search of its own.

Latest in Code Review & Git Flow

DEV Community
dev.to > mashi_mashi_3092153ef1ab5 > two-release-notes-per-release-one-for-users-one-for-future-me-2o69

Two Release Notes per Release: One for Users, One for Future Me

2+ day, 16+ hour ago   (307+ words) Every release I ship produces two different questions later. A user asks "what changed for me?" A month from now, I ask "why did I change it that way?" One document cannot answer both without getting long enough that nobody…...

TrendHunter.com
trendhunter.com > amp > trends > gitbook

AI Documentation Platforms: GitBook

3+ week, 2+ day ago   (232+ words) AI Documentation Platforms Trend Hunter Good product documentation can help customers understand a product, find answers, and ultimately decide whether to use or buy it, but keeping documentation useful and up to date can be challenging GitBook is a documentation…...

TrendHunter.com
trendhunter.com > trends > gitbook

AI Documentation Platforms

3+ week, 2+ day ago   (65+ words) GitBook Helps Teams Create Smarter Product Documentation AI Book Writer Turns Ideas Into Full Manuscripts With AI Assisted Writing RepoDoc Creates Clean GitHub Documentation From Your Repos In Seconds DeepDocs Keeps GitHub Documentation Up To Date With Your Codebase DocsBot…...

theregister
theregister.com > offbeat > 08/16/2026 > the-what-why-and-how-of-pull-requests-and-source-comments > 5287914

The what, why, and how of pull requests and source comments

4+ week, 19+ hour ago   (567+ words) Microsoft veteran on knowing the difference and convincing approvers to accept a change Veteran Microsoft engineer Raymond Chen has weighed in on the difference between a pull request description and comments embedded in the code. Both matter, but they serve…...