docs: improve documentation with inline config comments #144
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
eslint-github-bot
bot
added
the
documentation
|
@lumirlumir The CI seems to be failing, can you please check. |
|
Oh, I've found that it's a GitHub Actions server issue. Currently, my other PRs don't seem to be working correctly either.
|
|
okay, there's an ongoin incident https://www.githubstatus.com/incidents/cbdzqm5fw0fm |
Tanujkanti4441
added
the
accepted
… of https://github.com/eslint/css into docs-improve-documentation-with-inline-config-comments
snitin315
approved these changes
May 25, 2025
snitin315
deleted the
docs-improve-documentation-with-inline-config-comments
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.
Prerequisites checklist
What is the purpose of this pull request?
Hello,
In this PR, I've added inline config comments to the documentation for a better developer experience.
Users can now clearly verify the behavior with inline config comments.
What changes did you make? (Give an overview)
Related Issues
Is there anything you'd like reviewers to focus on?