[commit-queue.cfg] Create new project-scoped CQ config.

Autogenerated from ref-scoped cq.cfg located at:
  https://chromium.googlesource.com/custom-tabs-client/+/refs/heads/master/infra/config/cq.cfg
  (pinned https://chromium.googlesource.com/custom-tabs-client/+/746256f808a443831568e659c7e54143962d6b9b/infra/config/cq.cfg)

The new config is functionally equivalent to the old one. Upon landing, the new
config will take effect once LUCI config service picks it up. If you see
'commit-queue.cfg' in https://luci-config.appspot.com/#/projects/custom-tabs-client ,
then it has been picked up.

New commit-queue.cfg takes precedence over old cq.cfg, and once picked up makes
it safe to remove old cq.cfg.

See also internal PSA go/psa-migrate-to-commit-queue-cfg.

Generated-by: https://crrev.com/i/815809
Bug: chromium:916292
No-Try: True
Change-Id: Iaacad05bc24b1652f4820c912456be93806b267d
Reviewed-on: https://chromium-review.googlesource.com/c/1436768
Reviewed-by: Ryan Tseng <hinoka@chromium.org>
Commit-Queue: Andrii Shyshkalov <tandrii@chromium.org>
1 file changed
tree: 71909998d2f3f82d37b362b932f8554cbc30e94f
  1. codereview.settings
  2. commit-queue.cfg
  3. cr-buildbucket.cfg
  4. luci-logdog.cfg
  5. luci-milo.cfg
  6. OWNERS
  7. PRESUBMIT.py
  8. project.cfg
  9. README.md
README.md

Configuration for chrome infrastructure services