Skip to content

Add documentStageOverrides for document-only RFCs - #2

Open
magicmark wants to merge 1 commit into
graphql:mainfrom
magicmark:document-stage-overrides
Open

Add documentStageOverrides for document-only RFCs#2
magicmark wants to merge 1 commit into
graphql:mainfrom
magicmark:document-stage-overrides

Conversation

@magicmark

@magicmark magicmark commented Aug 26, 2026

Copy link
Copy Markdown

Summary

  • Adds a documentStageOverrides key to state.json so maintainers can set the stage for document-only RFCs (ones from graphql-wg/rfcs/ that have no associated spec PR or discussion with labels)
  • Marks MockSpec as superseded (stage "S")
  • Preserves the override through sync regeneration cycles

https://significant.inputfrom.ai/

Verification

After locally running:

GITHUB_TOKEN=$(gh auth token) npm run sync-rfcs
npm run compile && node build/src/render/build-site.js
Screenshot 2026-08-26 at 11 43 08 AM

(i didn't commit the state.json drift to minimize the amount of diff in this PR for easy minimal review - but we should set up a github action for that on a cronjob?)

cc @benjie @martinbonnin

Document-only RFCs (from graphql-wg/rfcs/) have no associated PR or
discussion labels, so their stage defaults to RFC 0. This adds a
documentStageOverrides key to state.json that lets maintainers set the
correct stage for these entries. Marks MockSpec as superseded.

Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
@magicmark
magicmark requested a review from benjie August 26, 2026 16:46
@magicmark
magicmark marked this pull request as ready for review August 26, 2026 16:46
@magicmark
magicmark requested a review from martinbonnin August 26, 2026 16:47

@martinbonnin martinbonnin left a comment

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Looks good to me. I'd argue if something is not a RFC, it may not belong to the RFC tracker but I'll defer to @benjie.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants