build: add header check to comply with TRG 7.02 #1029
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
ndr-brt
force-pushed
the
88-headers-check
branch
5 times, most recently
from
ff4ea26 to
a8212e2
Compare
ndr-brt
force-pushed
the
88-headers-check
branch
from
a8212e2 to
f3d2c82
Compare
ndr-brt
force-pushed
the
88-headers-check
branch
from
c3147bf to
c3ddaba
Compare
ndr-brt
force-pushed
the
88-headers-check
branch
from
44e0b56 to
bf084b6
Compare
paullatzelsperger
approved these changes
Feb 7, 2024
ndr-brt
force-pushed
the
88-headers-check
branch
4 times, most recently
from
9578941 to
0750ce7
Compare
ndr-brt
force-pushed
the
88-headers-check
branch
from
0750ce7 to
851a9d6
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.
WHAT
Add a check on checkstyle to ensure the headers are in the correct format according to TRG 7.02
WHY
TRG compliance
FURTHER NOTES
List other areas of code that have changed but are not necessarily linked to the main feature. This could be method signature changes, package declarations, bugs that were encountered and were fixed inline, etc.
Closes #88