0

add instructions for buganizer components

Give instructions for owners to add their individual buganizer
components to be automatically notified by the notifier.

link to proto:
[`dir_metadata` proto](https://source.chromium.org/chromium/infra/infra/+/HEAD:go/src/infra/tools/dirmd/proto/dir_metadata.proto)

Bug: 1418166
Change-Id: I61c26b7b9cdffefe672e4c9882290a045e28b56c
Reviewed-on: https://chromium-review.googlesource.com/c/chromium/src/+/4881260
Reviewed-by: Weizhong Xia <weizhong@google.com>
Reviewed-by: Jonathan Lee <jonathanjlee@google.com>
Commit-Queue: Nihar Damarasingu <nihardamar@google.com>
Cr-Commit-Position: refs/heads/main@{#1202857}
This commit is contained in:
nihardamar
2023-09-28 21:41:21 +00:00
committed by Chromium LUCI CQ
parent 5c31e23b6e
commit 3afa556646
2 changed files with 8 additions and 2 deletions
docs/testing
third_party/blink/tools

@ -213,14 +213,17 @@ introduce failures as long as test owners did not choose to opt-out the failure
notification mechanism. This includes new tests that fail in Chromium, as well
as new failures introduced to an existing test. Test owners are encouraged to
create an `DIR_METADATA` file in the appropriate `external/wpt/` subdirectory
that contains at least `monorail.component` fields, which will be used by the
importer to file the bugs.
that contains at least the `monorail.component` and `buganizer_public.component_id`
fields, which the importer will use to file bugs.
For example, `external/wpt/css/css-grid/DIR_METADATA` looks like:
```
monorail {
component: "Blink>Layout>Grid"
}
buganizer_public {
component_id: 1415957
}
team_email: "layout-dev@chromium.org"
```

@ -1,4 +1,7 @@
monorail {
component: "Blink>Infra"
}
buganizer_public {
component_id: 1415957
}
team_email: "blink-infra@chromium.org"