Mmastodon TechnologySoftware first seen 3 d ago, last 3 d ago, peak #2

Test repo run shows human code review can miss post-merge problems

Original: Three pull requests on a public test repo, with a person as approver: 1. Touched a covered file, waited, got a yes, merg

A developer describes a small experiment using three pull requests on a public test repository with a human reviewer. One change to covered files was approved and merged; an identical change was rejected with a stated reason; a third touched an area marked for post-merge checks and was merged immediately, with an issue surfacing seconds later.

Why now: It highlights how inconsistent human code review is and how deferred checks can let problems slip into the main branch.

smeldrpublic test repository

Open on mastodon →

Evidence

• Three pull requests on a public test repo, with a person as approver: 1. Touched a covered file, waited, got a yes, merged. 2. Same files, got a no with a reason, never merged. 3. Touched an Area we had set to check after the merge. It went in at once, and three seconds later… · smeldr · 1

API: https://socialmediatrends-api.osmike.com/v1/trends/4751025