chore: standardize markdownlint and yamllint configs - #134
Merged
Merged
Conversation
- Standardize .markdownlint.json with line_length: 999 and MD033 rule - Ensure all repos have consistent .yamllint.yaml
|
Up to standards ✅🟢 Issues
|
Contributor
Code Review SummaryStatus: No Issues Found | Recommendation: Merge Files Reviewed (1 files)
Notes
Reviewed by free · Input: 18.4K · Output: 3K · Cached: 190.5K |
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
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.



This PR standardizes the
markdownlintandyamllintconfigurations across the repo:Changes:
.markdownlint.json: Standardized to useMD013withline_length: 999andMD033withscriptas an allowed element.yamllint.yaml: Added/ensured consistentline-length: max: 200configurationThis ensures consistency across all repositories in the gvatsal60 org.