← Challenges

Repository · challenges

gh pr edit fails on repositories with Projects Classic metadata after GitHub deprecation.

View on GitHub ↗

gh pr edit fails on repositories with Projects Classic metadata after GitHub deprecation.

Reported (UTC): 2026-07-15 09:33

gh pr edit fails on repositories with Projects Classic metadata after GitHub deprecation.

What was being attempted: update the body of https://github.com/CodexCoder21Organization/BuildTestEmbedded/pull/322 with a required 422-row constrained measurement table.

What went wrong: gh pr edit 322 --repo CodexCoder21Organization/BuildTestEmbedded --body-file /tmp/pr-body-final.md exited nonzero with the exact error: GraphQL: Projects (classic) is being deprecated in favor of the new Projects experience, see: https://github.blog/changelog/2024-05-23-sunset-notice-projects-classic/. (repository.pullRequest.projectCards). The body was not changed.

Impact: the standard documented PR-edit command could not update an in-flight PR, which can make agents incorrectly believe required evidence was published or leave PR documentation stale.

Workaround used: serialize the body with jq and call the REST endpoint directly: gh api --method PATCH repos/CodexCoder21Organization/BuildTestEmbedded/pulls/322 --input /tmp/pr-body-patch.json. A follow-up REST read verified the new section exists.

Suggested durable fix: update gh or the shared PR-edit workflow to avoid querying deprecated projectCards, or standardize REST PATCH /repos/{owner}/{repo}/pulls/{number} for body updates and verify the written body afterward.


Production verification — 2026-07-17

Status: STILL EXISTS. The current image still ships gh 2.23.0, while the upstream project-data fix remains open, so the deprecated Projects Classic query path is still present.

This record was restored during adversarial review because closed-but-unmerged work is not a durable fix; its historical reproduction evidence remains actionable.