Add documentStageOverrides for document-only RFCs - #2
Open
magicmark wants to merge 1 commit into
Open
Conversation
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>
martinbonnin
approved these changes
Aug 26, 2026
martinbonnin
left a comment
There was a problem hiding this comment.
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.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
documentStageOverrideskey tostate.jsonso maintainers can set the stage for document-only RFCs (ones fromgraphql-wg/rfcs/that have no associated spec PR or discussion with labels)https://significant.inputfrom.ai/
Verification
After locally running:
(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