fix(CI): roll our own linter for YAML #3196
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
jbampton
force-pushed
the
fix-yaml-linter
branch
from
fcf690d
to
2b01538
Compare
Due to the ASF's policies changing we cannot use the original GitHub Actions for linting as they are not approved Lint Markdown for rules: - MD012/no-multiple-blanks - MD032/blanks-around-lists
jbampton
force-pushed
the
fix-yaml-linter
branch
from
2b01538
to
16d0bbf
Compare
|
Pinging @spacewander The Markdown and YAML linters seem to be working now 👍 |
gxthrj
approved these changes
Jan 5, 2021
spacewander
approved these changes
Jan 6, 2021
|
@jbampton |
This was referenced Jan 10, 2021
fix(CI): Update lint workflow so that the Markdown and YAML linters run
apache/apisix-dashboard#1254
Merged
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.
Due to the ASF's policies changing we cannot use the original GitHub Actions for linting as they are not approved
Lint Markdown for rules:
refs #3178
What this PR does / why we need it:
Fixes the YAML linter so we can continue to have standardized YAML.
Standardizes our Markdown.
Pre-submission checklist: