Content Quality: Clear News piece, 597 words (policy range for News: 400-1200; within range). Title is 105 characters, under the 150 cap. Standard Overview / What We Know / What We Don't Know structure.
Source Verification: Read from disk (gunzip) sources/2026-10/github-stacked-pull-requests-reach-general-availability-keeping-approvals-and-signatures-through-rebases/. source-0.html.gz (GitHub changelog, Oct 6 2026, 'Release', full post including Get started section and related posts, 200 OK, no archive fallback): confirms GA date (Oct 6, 2026); the two quoted phrases (opening sentence verbatim apart from initial capital; Charlie Marsh quote and 'Founder of Astral, OpenAI' verbatim); approvals preserved by Rebase stack 'when an otherwise unchanged stack is updated after its base branch... moves ahead... even in repositories that dismiss stale approvals'; 'GitHub creates signed replacement commits during Rebase stack, preserving original authorship' and automatic rebases after partial merges sign replacement commits 'when branch rules require signatures or any original commit was signed' (the changelog does not name a signing key and the article does not claim one); bypass permissions for lowest unmerged PR; stack enters and lands through merge queue as a single merge group, one merge commit per PR under the merge commit method; automatic retargeting when base branch is deleted; auto-merge 'rolling out over the next few weeks'; persistent header, Shift+J/Shift+K, timeline events, pull_request webhook 'stacked' action; gh stack extension 'now supports Git worktrees and includes several improvements'; 9% merged-code and 5% time-to-merge figures and 'over two-thirds of the top 1%'; 'available on all github.com plans and will be included in an upcoming GitHub Enterprise Server release'. Snapshot is the full post. source-1.html.gz (docs.github.com stacked pull requests landing page): supports exactly the two things it is cited for: the description 'break large code changes into a chain of smaller, dependent pull requests you can review and merge independently' (verbatim, within 'Use stacked pull requests to...') and the quickstart 'Install the gh stack extension in GitHub CLI'. The article makes no further claim from it. All 2 sources confirmed. github.blog and docs.github.com are both in config/source_allowlist.txt. The Aug public-preview cross-reference (/article/2026-08/19-github-brings-stacked-pull-requests-to-public-preview-with-new-gh-stack-cli-extension) resolves to an existing published article (preview announced July 30, published Aug 19); the article only says GA follows that preview and makes no preview-versus-GA comparison, so nothing is misstated. suspicious_patterns: null for both sources, nothing to evaluate.
Factual Accuracy: Every capability checked against the changelog and consistent with it. GA status is stated for the feature on github.com plans; GHES is correctly described as 'upcoming' without a date, and auto-merge for stacks is correctly described as still rolling out. The changelog does not call the gh stack extension itself GA or preview; the article does not either. Usage figures are attributed to GitHub, flagged as GitHub's own, methodology undisclosed, and not independently verified, as required.
Overall Assessment: Accurate, well-sourced, correctly caveated. All claims trace to the two cited first-party sources. APPROVE.