Lines Matching refs:to

9 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.
77 generally be relative to that point.
79 A few environment variables are set so scripts don't need to discover things.
83 * `REPO_PATH`: The path to the project relative to the root.
87 * `REPO_LREV`: The name of the remote revision, translated to a local tracking
97 A few keywords are recognized to pass down settings.  These are **not**
99 such will be expanded correctly via argument positions, so do not try to
102 * `${PREUPLOAD_FILES}`: List of files to operate on.
106 Some variables are available to make it easier to handle OS differences.  These
118 * `ignore_merged_commits`: If set to `true`, the hooks will not run on commits
123 This section allows for completely arbitrary hooks to run on a per-repo basis.
157 Note: Builtin hooks tend to match specific filenames (e.g. `.json`).  If no
170 Used to customize the behavior of specific `[Builtin Hooks]`.  Any arguments set
171 here will be passed directly to the linter in question.  This will completely
172 override any existing default options, so be sure to include everything you need
175 Quoting is handled naturally.  i.e. use `"a b c"` to pass an argument with
182 # Pass more filter args to cpplint.
188 Some builtin hooks need to call external executables to work correctly.  By
190 executables can be overridden through `[Tool Paths]`.  This is helpful to
208 # Or paths relative to the top of the git project.
210 # Or paths relative to the repo root.
220 * New hooks can be added in `rh/hooks.py`.  Be sure to keep the list up-to-date
225 If the return code of a hook is 77, then it is assumed to be a warning.  The
226 output will be printed to the terminal, but uploading will still be allowed
233   not easy to fix because the linters require not just the modified file but the
234   entire repo in order to perform full checks.  e.g. `pylint` needs to know what
235   other modules exist locally to verify their API.  We can support this case by
237   a lot.  Will need to consider a `PREUPLOAD.cfg` knob.
238 * We need to add `pylint` tool to the AOSP manifest and use that local copy