Repository navigation
Use WebAssembly/spec as the default upstream - #2262
Merged
Merged
Conversation
...for the resolve-baseline workflow. Just using the parent reported by the GitHub API is insufficient because most proposal repos are not actually forks of the spec repo as far as GitHub is concerned.
rossberg
approved these changes
Oct 3, 2026
Contributor
|
Ah, ok. My mistake, thought they were forks. |
Member
They would be, if it wasn't for GitHub's completely arbitrary restriction that you cannot fork within the same organisation, and it hence has to be done manually. |
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
3 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.
...for the resolve-baseline workflow. Just using the parent reported by the GitHub API is insufficient because most proposal repos are not actually forks of the spec repo as far as GitHub is concerned.