
Leave Copilot Approve Off
GitHub now prints a ready-to-approve assessment on every Copilot review. That line is a note. The admin switch that turns it into a required approval is off by default. Keep it off.
8 posts tagged with #Code-Review

GitHub now prints a ready-to-approve assessment on every Copilot review. That line is a note. The admin switch that turns it into a required approval is off by default. Keep it off.

A ranked cheat-sheet of five desk rules from this week: who pins the model, what .gitignore does not lock, who merges, who retries, and who still reads the diff.

The agent that writes the diff does not choose the model for that pull request. A named human pins the model before the session starts. Auto is a vendor default, not an owner.

A coding agent may open the pull request. A named human still owns the merge click. Treat GitHub agent merge and auto-merge as opt-in shortcuts, never as the default.

Use Git trailers, CI checks, and Git notes to make each commit carry a compact, reviewable handoff record.

A short AI-generated diff can cross validation, request, persistence, and test boundaries. Review the named code entities, the evidence, and the rollback seam—not only the lines that changed.

The first merge gate catches obvious AI coding mistakes. A repeatable review harness catches the slower failures: drift, missing rollback paths, weak tests, and agent changes that look fine until production maintenance begins.

A long-running coding agent can stay green after it changes directory. Production still needs a sandbox that survives /cd, a budget that counts nested work, and a human who owns both.
Also see: #Coding-Agents #Laravel #Vue #Change-Control #Code-Review
Type at least 2 characters to search.