[Yaml] Documented the github output format for the linter #14803
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
OskarStark
approved these changes
Jan 8, 2021
|
Thank you Javier. |
wouterj
reviewed
Jan 8, 2021
| @@ -33,6 +33,17 @@ The linter results can be exported to JSON using the ``--format`` option: | |||
| $ php bin/console lint:yaml translations/ --format=json | |||
| $ php bin/console lint:xliff translations/ --format=json | |||
|
|
|||
| When running the YAML linter inside `GitHub Actions`_, the output is automatically | |||
| adapted to the format required by GitHub, but you can force that format too: | |||
There was a problem hiding this comment.
I would not say "required". It's a nicer output in GitHub, but not required (the normal stdout works fine).
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.
Fixes #14583.