commit | 6ddd6db324d369ada1e8b1155291f0f94d08c3f2 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Fri Oct 19 12:30:45 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Fri Oct 19 12:30:45 2018 |
tree | 69d347ab405ae2461932a59b7f1171f058bf68a8 | |
parent | 18b75972df3e1d4eba158935b4e9ef1f781c5281 [diff] |
[isolate] Don't directly use SHA1 from tar_archiver.go. R=maruel@chromium.org, tandrii@chromium.org Change-Id: I876a6d39a39cb5a94121446c0defc225a76b7ec6 Reviewed-on: https://chromium-review.googlesource.com/c/1290105 Auto-Submit: Vadim Shtayura <vadimsh@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.