GHA: add prettier and eslint checks on the changed files for the pull request #6768
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 pull request
2 tasks
|
|
|
2 tasks
Test 🟢EvidenceFaillure
Success
|
asteriscos
deleted the
enhancement/6761-add-code-format-check-pull-request-workflow
branch
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.
Description
This pull request adds the Prettier and ESLint checks on the changed files for the pull requests workflow.
Issues Resolved
#6761
Test
We could test it creating a pull request with changes on the files that do not pass the code format of prettier and eslint. To test, you could use a fork to create the pull request and review the check result for the code formatting (prettier and linter).
Currently, the ESLint check is disabled for this repository, so we could ignore the test of this check.
Check List
yarn test:jest