commit | a98ff58647ec025a4e04ccc85edcc804923ca342 | [log] [tgz] |
---|---|---|
author | Vadim Shtayura <vadimsh@chromium.org> | Thu Dec 20 04:01:02 2018 |
committer | Commit Bot <commit-bot@chromium.org> | Thu Dec 20 04:01:02 2018 |
tree | 3f95c93079763bf042d9a11a607eb73e5d25b4d6 | |
parent | 82607619879e0e403f666fea49c137a2b8611f5c [diff] |
[lucicfg] Add graph.parents(...) query. It is like graph.children(...), but instead of returning direct children of a node, returns direct parents. Implemented almost identically, just follows the edges in the opposite direction. R=tandrii@chromium.org, nodir@chromium.org BUG=833946 Change-Id: I4bde09762de63a6c1e1deaf857fdbfa7f5e1395e Reviewed-on: https://chromium-review.googlesource.com/c/1385667 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Nodir Turakulov <nodir@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.