fix: CI by pointing to experimentation branch (experimental) #9284
+2
−2
Conversation
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
|
Note that the CI will not pass here until google/blockly-keyboard-experimentation#684 is merged, so I'll be waiting on putting this into review until that point (so that passing CI can be verified). |
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.
The basics
The details
Resolves
Fixes #9283
Proposed Changes
Updates the keyboard navigation plugin workflow to point to the screen reader experimentation branch.
Reason for Changes
This ensures that both the plugin (via google/blockly-keyboard-experimentation#684) and core Blockly correctly link their experimental screen reader branches against each other to ensure CI passes correctly for both.
Test Coverage
No new tests are needed here.
Documentation
N/A
Additional Information
Similar to #9280, this PR will never be merged directly into
developso the workflow changes will remain isolated to the experimental branch.