Make sure the code in the repo is correctly formatted by automatically checking the format on every PR.
Motivation and Context
Automatically keep the code format consistent.
How Has This Been Tested?
Pushed a commit (897790993fa8e4d6133751697aac6e12824165ec) with a formatting error. CI fails.
Types of changes
[ ] Bug fix (non-breaking change which fixes an issue).
[ ] New feature (non-breaking change which adds functionality).
[ ] Breaking change (fix or feature that would cause existing functionality to not work as expected).
Checklist:
[x] It is my own work, its copyright is implicitly assigned to the project and no substantial part of it has been copied from other sources (including Stack Overflow). In rare occasions this is acceptable, like in CMake modules where the original copyright information should be kept.
[x] I'm using the same code standards as the existing code (indentation, spacing, variable naming, ...).
[ ] I've added tests for my code.
[x] I have verified whether my change requires changes to the documentation
[x] My change either requires no documentation change or I've updated the documentation accordingly.
[x] My branch has been rebased to main, keeping only relevant commits.
Summary
Check code format on PR and main branch.
Details
Make sure the code in the repo is correctly formatted by automatically checking the format on every PR.
Motivation and Context
Automatically keep the code format consistent.
How Has This Been Tested?
Pushed a commit (897790993fa8e4d6133751697aac6e12824165ec) with a formatting error. CI fails.
Types of changes
Checklist: