Install
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.
Related topics
Latest in Code Review & Git Flow
GitHub Learning Labs Now Open For Newbies
31+ min ago (447+ words) Once you know your way around GitHub its difficult to remember how it felt when it was an unfamiliar environment with its strange jargon of Commits, Issues, Pull Requests and so on. The newly launched GitHub Learning Lab has a…...
Turn Your GitHub Contribution Graph Into an ASCII City
5+ hour, 16+ min ago (1244+ words) Generates animated SVGs for profile READMEs I decided that a normal GitHub contribution graph is not enough. So I turned mine into a city. And I wanted to share it so you can too. I made Skyline, a small Go…...
Name the Writable Surface Before You Accept the Diff
40+ min ago (1602+ words) Consider a composite review incident, not a log from this account. A billing test failed in the afternoon. The assertion wanted 3 and got 4. The task note asked for a fix and a short pull-request comment. A session summary came back…...
Freeze User-Visible Strings Before an OSS Patch Hits Review
56+ min ago (930+ words) Most OSS suites protect control flow rather than the exact bytes that leave the process. Assertions check status codes, exception types, and structured fields, while the human-readable remainder stays unpinned. Formatters and AI review passes then treat that remainder as…...
Match the Repo Test Dialect Before an OSS Patch Leaves the Fork
56+ min ago (320+ words) House dialect is not the same thing as clean code in the abstract. Neighboring tests already show how the project fakes time, sockets, clocks, and HTTP backends. Copying that local grammar keeps the review focused on behavior instead of on…...
Convert CONTRIBUTING.md Into an Executable Preflight Gate Before an OSS Patch Leaves Your Fork
1+ hour, 4+ min ago (686+ words) A contributor spends a weekend on a null-dereference fix, opens the pull request on Monday morning, and watches CI fail on a rule that CONTRIBUTING.md stated in paragraph nine. The patch logic is correct, but the branch name lacks…...
GitHub adds AI to catch passwords before a code push
1+ hour, 29+ min ago (488+ words) GitHub has announced an AI detector, developed with Microsoft Applied Sciences, to help prevent developers from uploading passwords and other credentials to code repositories. The ModernBERT-based classifier will expand GitHub’s push protection, which checks code for secrets and can block…...
FAQ: A Desk Checkout Is Not the Pipeline Snapshot
1+ hour, 36+ min ago (1279+ words) I keep hearing one claim in pipeline reviews. The YAML is open, so the pipeline must be real. Is a desk checkout the snapshot GitLab will create? I do not treat those two as the same object. A worktree can…...
FAQ: A Free Shell Is Not Your GitLab Runner
1+ hour, 36+ min ago (1252+ words) I keep seeing one shortcut in review threads. Someone debugs a GitLab job on a free shell. Then they treat that shell like the project runner. That shortcut feels fast when the review is late. It also mixes three different…...
The Merge Bit Stays With the Owner
2+ hour, 10+ min ago (282+ words) Protected paths do not become optional when a contribution surge arrives. A free model can draft a note about a diff. It cannot own the merge bit, dismiss a scanner, or stand in for the human named in CODEOWNERS. Early…...