[v1.5] Format with prettier
#2771
Draft
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
jdbaldry
force-pushed
the
grafana-alloy-v1.5-jdb/2025-02-reverse-prettier-changes
branch
2 times, most recently
from
1af8070 to
eb289aa
Compare
Consistent formatting improves readability and makes it easier for tools to transform the source. The general human understanding of Markdown has some ambiguities so it's possible this PR will break some documentation presentation because the formatter follows the CommonMark specification. Elminating this ambiguity provides more consistent behavior and makes it easier for future readers to understand your Markdown. Consistent formatting is also necessary to provide meaningful diffs in future automated PRs. If you would like to benefit from automated improvements made by the Docs Platform team, you must adopt `prettier` in your local development and enforce it in CI. If you would like help running `prettier` in CI, reach out in the [#docs-platform Slack channel](https://raintank-corp.slack.com/archives/C07R2REUULS). Created-By: reverse-changes Repository: grafana/alloy Website-Pull-Request: grafana/website#24071
jdbaldry
force-pushed
the
grafana-alloy-v1.5-jdb/2025-02-reverse-prettier-changes
branch
from
eb289aa to
9350e83
Compare
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.
Consistent formatting improves readability and makes it easier for tools to transform the source.
The general human understanding of Markdown has some ambiguities so it's possible this PR will break some documentation presentation because the formatter follows the CommonMark specification.
Elminating this ambiguity provides more consistent behavior and makes it easier for future readers to understand your Markdown.
Consistent formatting is also necessary to provide meaningful diffs in future automated PRs.
If you would like to benefit from automated improvements made by the Docs Platform team, you must adopt
prettierin your local development and enforce it in CI.If you would like help running
prettierin CI, reach out in the #docs-platform Slack channel.Created-By: reverse-changes
Repository: grafana/alloy
Website-Pull-Request: https://github.com/grafana/website/pull/24071