Add some keywords to make it easier to find Impact-None

Code behind a command line flag has no security impact, so gets tagged
with the Impact-None hotlist.

Change-Id: I3bc794e0fe038c67e0306095aa84755ce9cecafb
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/5273723
Reviewed-by: Adrian Taylor <adetaylor@chromium.org>
Commit-Queue: Adrian Taylor <adetaylor@chromium.org>
Auto-Submit: danakj <danakj@chromium.org>
Cr-Commit-Position: refs/heads/main@{#1258080}

This commit is contained in:

danakj

2024-02-08 19:30:01 +00:00

committed by

Chromium LUCI CQ

parent f7e1ba300d

commit 3b491996d3

1 changed files with 2 additions and 1 deletions

									
										3

docs/security/shepherd.md
									
				@ -251,7 +251,8 @@ it’s important to get the severity as correct as possible.

				We do not release severe security regressions, so we need to know the earliest

				impacted Chrome release branch.

				First, if an issue [doesn’t impact Chrome users by default, add the hotlist

				First, if an issue [doesn’t impact Chrome users by default (such as be being

				behind a disabled feature or a command line flag), add the hotlist

				**`Security_Impact-None`**](security-labels.md#when-to-use-security_impact_none-toc_security_impact_none);

				otherwise, set a **Found In** milestone in the `Found In` field as follows:

Add some keywords to make it easier to find Impact-None

3 docs/security/shepherd.md

3

docs/security/shepherd.md