Build 13: Staging #1303
Merged
Build 13: Staging #1303
Conversation
This file contains 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
|
The latest updates on your projects. Learn more about Vercel for Git ↗︎
|
horacioh
force-pushed
the
build13/staging
branch
from
faba675
to
efbe205
Compare
burdiyan
force-pushed
the
build13/staging
branch
from
555a209
to
efbe205
Compare
Removing workspace-hack, because it seems to be causing issues, and seems like it's not worth the effort at this point.
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.
During Build 13 we use the build13/staging branch as if it was master, to keep the nightly builds from being broken.
The PR is here to ensure tests pass.
To Do
/.well-knownpath. Add the specifier.