fix: install chrome dependencies
#6
Merged
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
# for free
to join this conversation on GitHub.
Already have an account?
# 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.
This pull request includes changes to the
.github/workflows/coverage.yamlfile to improve the setup process for Chrome dependencies. The most important changes include adding a step to install necessary Chrome dependencies and modifying the existing setup to avoid redundant installations.Improvements to Chrome setup:
.github/workflows/coverage.yaml: Added a new step to install Chrome dependencies only if the branch ismain. This ensures that the required libraries are available for Chrome to run correctly..github/workflows/coverage.yaml: Modified theSetup Chromestep to skip installing dependencies, as they are now installed in a separate step. This prevents redundant installations and speeds up the workflow.