commit | d3e8adbbd83b503e6e473f6d5683e6aad6edea3f | [log] [tgz] |
---|---|---|
author | Takuto Ikuta <tikuta@chromium.org> | Tue May 21 14:06:49 2019 |
committer | Commit Bot <commit-bot@chromium.org> | Tue May 21 14:06:49 2019 |
tree | 306062994c81d028ad997f909fb81cef79b67874 | |
parent | 96c1e38c0f4acfbd0fb6077e8161218eb53321c3 [diff] |
[downloader] follow up for crrev.com/c/1619575/7 This is follow up CL for https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1619575/7 Bug: 962804 Change-Id: If2a79bec18671f84a630f80f2224b64e4c891d0c Reviewed-on: https://chromium-review.googlesource.com/c/infra/luci/luci-go/+/1621888 Auto-Submit: Takuto Ikuta <tikuta@chromium.org> Reviewed-by: Marc-Antoine Ruel <maruel@chromium.org> Commit-Queue: Marc-Antoine Ruel <maruel@chromium.org>
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.