[0.71] Update Policheck exclusions and exceptions 9/15 (#12141)
This PR backports #12139 to 0.71. It seems the Policheck tasks no longer accept blanket "exclusions" in our rules database for terms we use everywhere. So I've gone and updated the individual "file exceptions" for those terms in our database. It's harder to maintain, but this should unblock PRs. - Bug fix (non-breaking change which fixes an issue) Compliance. Updated rules database. N/A N/A Should this change be included in the release notes: no
This commit is contained in:
Родитель
a67f0755ab
Коммит
0b57e95b18
|
@ -8,7 +8,7 @@ NOTE: Use ALL CAPS for excluded terms below else it will silently ignore them. A
|
||||||
<PoliCheckExclusions>
|
<PoliCheckExclusions>
|
||||||
<!-- Each of these exclusions is a folder name -if \[name]\exists in the file path, it will be skipped -->
|
<!-- Each of these exclusions is a folder name -if \[name]\exists in the file path, it will be skipped -->
|
||||||
<Exclusion Type="FolderPathFull">
|
<Exclusion Type="FolderPathFull">
|
||||||
.GIT|ARM|ARM64|BUILD|DIST|GENERATED FILES|NODE_MODULES|OUTPUT|TARGET|X64|X86|PATCHES
|
.GIT|ARM|ARM64|BUILD|DIST|GENERATED FILES|NODE_MODULES|OUTPUT|TARGET|X64|X86|PATCHES|LIB-COMMONJS
|
||||||
</Exclusion>
|
</Exclusion>
|
||||||
<!-- Each of these exclusions is a folder name -if any folder or file starts with "\[name]", it will be skipped -->
|
<!-- Each of these exclusions is a folder name -if any folder or file starts with "\[name]", it will be skipped -->
|
||||||
<Exclusion Type="FolderPathStart">
|
<Exclusion Type="FolderPathStart">
|
||||||
|
|
Двоичные данные
.ado/config/PoliCheckRules.mdb
Двоичные данные
.ado/config/PoliCheckRules.mdb
Двоичный файл не отображается.
Загрузка…
Ссылка в новой задаче