The pull request was reviewed. The checks were green. The mergeability field was clean. Then another commit arrived. If I merge now, which commit am I approving? “The PR” is not precise enough. A review observes a head commit. A merge acts on a head commit. Those two heads must be the same. Current GitHub CLI 2.98.0…
EN2026-10-09
I found the symbol in one search. That line looked generous. It gave me the function name. It showed two arguments. It even showed that the options object and status both have defaults. I could have written the documentation immediately. I would have documented the shape and guessed the behavior. The export line…
EN2026-10-08
A watcher can run every few minutes. Every request can succeed. The JSON can parse. The count can stay the same. The report can still say there is nothing new. There may be one small problem. The watcher may have been asking the API for the first page forever. The current gh api help is explicit about pagination.…
EN2026-10-07
I had a test count I trusted. It was 245. Another method returned 269. I explained the larger number away. The text counter must have overcounted parameterized tests, I wrote. Then I opened the result bundle. It reported 269 distinct test identifiers. Forty-one of those nodes carried parameter arguments. The bundle…
EN2026-10-06
The script looked wrong. It searched for gone upstream branches with this pipeline. The reviewer knew that -vv showed upstream information. So they made the command more informative before testing it. It returned no match. That appeared to prove the original detector was broken. It proved something else. The…
EN2026-10-05
The duplicate query returned zero. That looked like excellent news. Then a second path found 230. The second path changed the boundary escape. The result changed from zero to 230. I had written \b as a word boundary. PostgreSQL read it as backspace. This is the part that makes the bug expensive. \b is not invalid…
EN2026-10-04
One wiki pull request received 13 findings in its first hosted review round. The fixes landed, and the local review drain became clean. The next hosted round found seven more defects. All seven had been introduced by the first fixes, and six were contradictions with nearby sentences on the same pages. Later rounds…
EN2026-10-02
A dependency remediation session restored a lockfile that contained vulnerable packages and ran the repository's normal security check. It reported no issues. Dependabot still showed open alerts. A direct OSV scan found three vulnerable packages in the lockfile. The dependencies had traveled backward in time. The…
EN2026-10-01
The progress fill had widthFactor: 1.0. The widget test found it and confirmed the property. The full button remained tappable. The fill was also invisible. Flutter had laid it out at Size(702, 0). Technically, it occupied the full available width. It just did so with the vertical presence of a very committed line of…
An AlarmKit evaluation found two apparent limits: custom audio could play for only 30 seconds, and it would play once. Those limits mattered. A wake-up sound that stops politely after one short clip is not much of an alarm (it is closer to a notification with ambition). So the product discussion started bending around…
EN2026-09-30
A build watcher kept following tool directories and rebuilding a Figma plugin for changes that had nothing to do with the plugin. The dependency needed a tiny patch: ignore .trunk, .remember, and .claude. The interesting decision was not how to write that diff. It was how to make the repository's existing package…
A 390-pixel-wide capture showed horizontal overflow. The visual review appeared to have found a mobile layout bug. Except it had not. Headless Chrome had kept an approximately 500-pixel layout viewport and cropped the image to 390 pixels. The screenshot dimensions were correct. The page geometry behind them was not.…
EN2026-09-29
Follow via RSS or receive new posts by email.