commit | 8a1c8ec1982c117ba75d2cafed878dd29d585572 | [log] [tgz] |
---|---|---|
author | Weiwei Lin <weiweilin@google.com> | Wed Sep 23 04:22:40 2020 |
committer | LUCI CQ <infra-scoped@luci-project-accounts.iam.gserviceaccount.com> | Wed Sep 23 04:22:40 2020 |
tree | 43e76001e05e057bb4aa2bb58b7057edd9b1a80c | |
parent | b35d4158179ee8c3b994af624805e7463b26d8f8 [diff] |
[resultui] open legacy build page in the current tab instead Reaons: 1. The legacy build page is not a sub-resource of the build page. 2. It's unlikely that users will need both the new and old build pages at the same time. R=nqmtuan@google.com, orodley@google.com Change-Id: Id6a1b1a65196fcb6c9e7102881ea110ae9191dd4 Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/2423810 Auto-Submit: Weiwei Lin <weiweilin@google.com> Reviewed-by: Quang Minh Tuan Nguyen <nqmtuan@google.com> Commit-Queue: Quang Minh Tuan Nguyen <nqmtuan@google.com>
LUCI Go code is meant to be worked on from an Chromium infra.git checkout, which enforces packages versions and Go toolchain version. First get fetch via depot_tools.git then run:
fetch infra cd infra/go eval `./env.py` cd src/go.chromium.org/luci
Contributing uses the same flow as Chromium contributions.