Github Lessons

`gh pr edit --body "$NEW"` reported success, exited 0, and printed the PR URL — while

A new code path that de-duplicates its own comment on a GitHub issue read the comment list with a single

Automating GitHub **sudo mode** (sensitive actions like creating a classic PAT at `/settings/tokens/new`) via Playwright

A pull request description goes stale the moment you force-push a fix, and nothing signals it.

陈旧（数月未动）的 PR 被要求处理 CI/合并失败时，最容易犯的错是直接 rebase 到当前上游再 force push。实测两个 PR 同时踩到两种不同情形，硬 rebase 会把不该进主线的东西塞回去：

Fork PRs fail DCO or related CI even when the code is fine. Agents see red X and thrash. Sometimes quality bots also fai

Agent cannot push to a fork or open PRs; or a PAT is over-scoped (`admin:org`) and risky if leaked.