Lines Matching refs:to
7 turn on any hook it wishes to enforce.
13 Normally these execute automatically when you run `repo upload`. If you want to
20 Sometimes you might want to bypass the upload checks. While this is **strongly
23 `--no-verify` when running `repo upload` to skip all upload checks. This will
42 Simply check this in to the manifest git repo and you're done.
53 in subdirectories (to try and override parent settings) is not supported.
80 generally be relative to that point.
82 A few environment variables are set so scripts don't need to discover things.
86 * `REPO_PATH`: The path to the project relative to the root.
90 * `REPO_LREV`: The name of the remote revision, translated to a local tracking
100 A few keywords are recognized to pass down settings. These are **not**
102 such will be expanded correctly via argument positions, so do not try to
105 * `${PREUPLOAD_FILES}`: List of files to operate on.
106 * `${PREUPLOAD_FILES_PREFIXED}`: A list of files to operate on.
107 Any string preceding/attached to the keyword ${PREUPLOAD_FILES_PREFIXED}
109 to the keyword, the previous argument will be repeated before each file.
113 Some variables are available to make it easier to handle OS differences. These
141 * `ignore_merged_commits`: If set to `true`, the hooks will not run on commits
146 This section allows for completely arbitrary hooks to run on a per-repo basis.
156 You do not need to send stderr to stdout. The tooling will take care of
175 code. Refer to go/test-mapping for more details.
187 * `commit_msg_relnote_for_current_txt`: Check that CLs with changes to
196 * `pylint`: Alias of `pylint2`. Will change to `pylint3` by end of 2019.
202 Note: Builtin hooks tend to match specific filenames (e.g. `.json`). If no
215 Used to customize the behavior of specific `[Builtin Hooks]`. Any arguments set
216 here will be passed directly to the linter in question. This will completely
217 override any existing default options, so be sure to include everything you need
220 Quoting is handled naturally. i.e. use `"a b c"` to pass an argument with
227 # Pass more filter args to cpplint.
234 This section can only be added to the repo project-wide settings
238 Used to explicitly exclude some projects when processing a hook. With this
239 section, it is possible to define a hook that should apply to the majority of
244 quotes. For advanced cases, it is possible to use a [regular
254 # hardware/ will be excluded except for ones starting with hardware/google (due to
261 Some builtin hooks need to call external executables to work correctly. By
263 executables can be overridden through `[Tool Paths]`. This is helpful to
286 # Or paths relative to the top of the git project.
288 # Or paths relative to the repo root.
298 * New hooks can be added in `rh/hooks.py`. Be sure to keep the list up-to-date
303 If the return code of a hook is 77, then it is assumed to be a warning. The
304 output will be printed to the terminal, but uploading will still be allowed
311 not easy to fix because the linters require not just the modified file but the
312 entire repo in order to perform full checks. e.g. `pylint` needs to know what
313 other modules exist locally to verify their API. We can support this case by
315 a lot. Will need to consider a `PREUPLOAD.cfg` knob.
316 * We need to add `pylint` tool to the AOSP manifest and use that local copy