prettier: Disable for markdown files #12333
Merged
+2
−2
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
This is causing more pain than it is worth, especially since the prettier check currently only runs in the frontend test suite, so if a backend pull request introduces a new markdown file the CI will fail on some future run instead of on the PR. Sure, we can fix that, but is it worth the complexity? IMHO no.
Turbo87
added
C-internal 🔧
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
2 participants
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 is causing more pain than it is worth, especially since the prettier check currently only runs in the frontend test suite, so if a backend pull request introduces a new markdown file the CI will fail on some future run instead of on the PR. Sure, we can fix that, but is it worth the complexity? IMHO no.