Update GAP numbering system to use PR number#11
Merged
Conversation
magicmark
force-pushed
the
gap_numbering_and_discussion
branch
from
April 30, 2026 04:49
94b19ce to
c9091e4
Compare
Closed
magicmark
force-pushed
the
gap_numbering_and_discussion
branch
4 times, most recently
from
April 30, 2026 04:54
5c39ea6 to
360046c
Compare
magicmark
force-pushed
the
gap_numbering_and_discussion
branch
from
April 30, 2026 04:56
360046c to
b0b2672
Compare
benjie
approved these changes
Apr 30, 2026
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
2 participants
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.
As discussed at March 5th WG meeting and voted on by the TSC, we are updating the numbering system for GAPs to use the number of the GitHub Pull Request instead of an assigned number.
We may still decide to have buckets/categories/namespaces for the purposes of displaying GAPs on the index page -- we can follow up with this (perhaps uses
tagsor some newcategoryfield in metadata.yml)cc @benjie