Redo dotnet format #5119
Merged
Redo dotnet format #5119
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
surfnerd
approved these changes
Mar 15, 2021
|
|
|
BTW, if anyone else runs into pre-commit issues after this commit, you have to have |
1 task
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
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.
Proposed change(s)
Now that
dotnet-formathas upstream support, we can remove the hacky script and just use the provided hook.Note: requires
identity>=2.1.2installed to run with pre-commit locally.Useful links (Github issues, JIRA tickets, ML-Agents forum threads etc.)
dotnet/format#872
Types of change(s)