Repository navigation
Run Playwright against beta rather than staging on main - #1372
Merged
Merged
Conversation
Beta is public at python.microbit.org/v/beta, while staging is internal, and the two builds differ only in base path. This matches ml-trainer, including its rule for when main doesn't build beta.
|
Preview build will be at |
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
1 participant
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.
main builds staging and beta, and Playwright runs in one of them. Beta is public at python.microbit.org/v/beta, while staging is internal, and the two builds differ only in base path, so test beta.
The rule is ml-trainer's (
bin/print-web-stages.cjs): test beta when the ref builds it, otherwise the one non-production stage. It carries over unchanged if python gets ml-trainer's beta branch logic.