diff options
| author | Jonas Toth <jonas.toth@gmail.com> | 2018-12-10 19:41:53 +0000 |
|---|---|---|
| committer | Jonas Toth <jonas.toth@gmail.com> | 2018-12-10 19:41:53 +0000 |
| commit | e740145e19b74a98c82d9870b93f9b1c306c20d4 (patch) | |
| tree | 25bf0146f1d21105131312d2cdb6fba260bd7e17 /clang/lib/CodeGen/ModuleBuilder.cpp | |
| parent | c1b2d5905a1c7a27a570567433a6fa22efde3a29 (diff) | |
| download | llvm-e740145e19b74a98c82d9870b93f9b1c306c20d4.zip llvm-e740145e19b74a98c82d9870b93f9b1c306c20d4.tar.gz llvm-e740145e19b74a98c82d9870b93f9b1c306c20d4.tar.bz2 | |
[clang-tidy] insert release notes for new checkers alphabetically
Summary:
Almost all code review comments on new checkers {D55433} {D48866} {D54349} seem to ask for the release notes to be added alphabetically, plus I've seen commits by @Eugene.Zelenko reordering the lists
Make add_new_check.py add those release notes alphabetically based on checker name
If include-fixer section is seen add it at the end
Minor change in the message format to prevent double newlines added before the checker.
Do the tools themselves have unit tests? (sorry new to this game)
- Tested adding new checker at the beginning
- Tested on adding new checker in the middle
- Tested on empty ReleasesNotes.rst (as we would see after RC)
Patch by MyDeveloperDay.
Reviewers: alexfh, JonasToth, curdeius, aaron.ballman, benhamilton, hokein
Reviewed By: JonasToth
Subscribers: cfe-commits, xazax.hun, Eugene.Zelenko
Tags: #clang-tools-extra
Differential Revision: https://reviews.llvm.org/D55508
llvm-svn: 348793
Diffstat (limited to 'clang/lib/CodeGen/ModuleBuilder.cpp')
0 files changed, 0 insertions, 0 deletions