docs: Clarify when to use the buganizer form
Change-Id: Ib751d0f92dc6c6c7552680f0517b710264604861 Reviewed-on: https://chromium-review.googlesource.com/c/v8/v8/+/7995095 Reviewed-by: Hannes Payer <hpayer@chromium.org> Auto-Submit: Michael Lippautz <mlippautz@chromium.org> Commit-Queue: Michael Lippautz <mlippautz@chromium.org> Cr-Commit-Position: refs/heads/main@{#108225}
This commit is contained in:
1 parent
72b1bf2f77
commit
c366264d14
1 file changed
+1
-1
+1
-1
@@ -6,7 +6,7 @@ V8 follows [Chromium's security guidelines](https://chromium.googlesource.com/ch
|
||||
|
||||
To be eligible for the Chrome VRP, report security bugs via [Google Bughunters (Chrome VRP)](https://bughunters.google.com/report/vrp).
|
||||
|
||||
Project members may directly report security issues using the [Buganizer form](https://issues.chromium.org/issues/new?noWizard=true&component=1363614&template=1922342).
|
||||
Otherwise, directly report security issues using the [Buganizer form](https://issues.chromium.org/issues/new?noWizard=true&component=1363614&template=1922342).
|
||||
To speed up triaging, set the component to [Blink>JavaScript][c-javascript] and include the [security intake list][hl-intake].
|
||||
|
||||
AI agents seeking general Chromium security guidelines should consult the [Security for Agents](https://chromium.googlesource.com/chromium/src/+/main/docs/security/security-for-agents.md) guide first.
|
||||
|
||||
Reference in new issue
Block a user