chore: remove trailing whitespaces #4993
Open
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
Signed-off-by: Ludovic Terrier <[email protected]>
|
|
clayton-cornell
added
the
type/docs
clayton-cornell
approved these changes
Dec 3, 2025
Contributor
clayton-cornell
left a comment
clayton-cornell
left a comment
There was a problem hiding this comment.
Approving for the doc changes. I'll leave the code changes to @grafana/grafana-alloy-maintainers for their check :-)
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
3 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.
PR Description
Remove all trailing whitespaces in the entire repository.
Which issue(s) this PR fixes
We are using the Alloy mixins, but the jsonnet files contain trailing whitespaces that conflict with our pre-commit hooks every time we sync with upstream. This PR is a one-shot run using
pre-committo remove all existing trailing whitespaces.Notes to the Reviewer
A more future-proof solution would be to add this kind of check to this repository. Since you don't use pre-commit, what would be the recommended approach for maintaining this standard going forward?
PR Checklist
As this is a cosmetic/non-functional change, I don't know if the CHANGELOG.md needs to be updated?