Run dprint in copilot-setup-steps to prevent network blocking error #1269
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
Contributor
There was a problem hiding this comment.
Pull Request Overview
This PR adds a step in the GitHub Actions workflow to pre-fetch dprint caches before network restrictions apply, preventing failures when fetching Wasm blobs.
- Introduces a shell comment and a run step for formatting checks
- Ensures dprint's cache is pulled early in the setup
Comments suppressed due to low confidence (1)
.github/workflows/copilot-setup-steps.yml:30
- The command 'npx hereby check:format' appears incorrect. It should be something like 'npx dprint check-format' to actually invoke dprint formatting checks.
- run: npx hereby check:format
RyanCavanaugh
approved these changes
Jun 24, 2025
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.
If this isn't done, runs will fail because the network blocks these requests for the Wasm blobs.