Cargo fmt #2009
Merged
Cargo fmt #2009
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
Keats
pushed a commit
that referenced
this pull request
Feb 16, 2023
* Run cargo fmt * Add cargo fmt --check to pipeline
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.
Have you checked to ensure there aren't other open Pull Requests for the same update/change?
Are you doing the PR on the
nextbranch?This PR runs
cargo fmtand addscargo fmt --checkto the pipeline to prevent future PRs from being merged without proper formatting in the future. This is something that has happened in the past:Having everything be formatted always avoids having unexpectedly large diffs when someone uses format-on-save and doesn't turn it off.
The formatting was not that far off from what
cargo fmtgives us so it shouldn't cause that many conflicts.