| commit | eced1e748c8a870d406b90994a5739c4db8036a8 | [log] [tgz] |
|---|---|---|
| author | Vadim Shtayura <vadimsh@chromium.org> | Fri Feb 22 19:37:37 2019 |
| committer | Commit Bot <commit-bot@chromium.org> | Fri Feb 22 19:37:37 2019 |
| tree | 7bc00ea18f56d1fe990c7d2c0a9cf5bd327531f1 | |
| parent | e0c40046aaac45aec78b730726d5c2290fc5942a [diff] |
[lucicfg] Strongly suggest to use a shebang for entry point scripts. Like this: "#!/usr/bin/env lucicfg generate". lucicfg will keep nagging with warnings in stderr until it is added. Multiple users already mistakenly used `lucicfg generate <wrong *.star file>` for generating Swarming's bots.cfg and were very confused by its output (usually some import errors because the package root is wrong). Distinguishing entry point scripts with '#!...' seems like the simplest option for now that also does no harm in the future when we have a better approach. R=tandrii@chromium.org BUG=833946 Change-Id: Ib84595491fb944754808a022705e04be00730c13 Reviewed-on: https://chromium-review.googlesource.com/c/1482574 Commit-Queue: Vadim Shtayura <vadimsh@chromium.org> Reviewed-by: Andrii Shyshkalov <tandrii@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.