Repository navigation
Conversation
As voted on in today's CG meeting.
Member
Author
|
@tlively the automation works! but it requires someone to approve the workflow to run. I'll look into that tomorrow. |
tlively
approved these changes
Oct 7, 2026
tlively
reviewed
Oct 7, 2026
| "extended-name-section": { | ||
| "name": "Extended Name Section", | ||
| "url": "https://github.com/WebAssembly/extended-name-section", | ||
| "phase": 2, |
Member
There was a problem hiding this comment.
Should we move this up to be co-located with the other phase 3 proposals, or do we not care about the order? Maybe we should just alphabetize the list if we don't want to have to remember to move things around.
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 voted on in today's CG meeting.