elevate formatting issues to build failure #11098
Merged
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
9265b78 to
c659856
Compare
c659856 to
0329e74
Compare
sebasgomez238
approved these changes
Dec 19, 2024
JamieMagee
approved these changes
Dec 19, 2024
ryanbrandenburg
approved these changes
Dec 19, 2024
0329e74 to
44a4a48
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.
The NuGet updater already enforces code formatting as a CI check, but this ensures the formatting failures are raised as errors in the build and appear in the IDE. This makes finding and fixing them much easier so a CI cycle isn't wasted.
This PR contains a temporary commit that introduces a formatting error to verify the CI fails as expected. Onec verified this commit will be removed.Temporary commit resulted in the expected build error in CI.