Remove trailing whitespace from a variety of files#532
Closed
floatingatoll wants to merge 1 commit intomozilla-iam:masterfrom
Closed
Remove trailing whitespace from a variety of files#532floatingatoll wants to merge 1 commit intomozilla-iam:masterfrom
floatingatoll wants to merge 1 commit intomozilla-iam:masterfrom
Conversation
floatingatoll
force-pushed
the
yaml-whitespace
branch
from
37bf500 to
5860322
Compare
This was referenced Jul 27, 2021
Contributor
Author
|
Replaced by #540. |
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
1 participant
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.
#528 included fixes for trailing whitespace in a variety of files, which I imagine we should fix regardless of #528 itself. These don't seem to be caught by CI, so this probably will not need to be merged into the CI PR I'm expecting to end up creating out of several other PRs.
Reviewers, my biggest concern is that this ought to be a no-op, but if it will trigger lambda autodeploys or other unknown things, then that would be of concern.