Lines Matching refs:is

20 Sometimes you might want to bypass the upload checks.  While this is **strongly
52 This file is checked in the top of a specific git repository.  Stacking them
53 in subdirectories (to try and override parent settings) is not supported.
91    branch. This is typically latest commit in the remote-tracking branch.
95 * `PREUPLOAD_COMMIT`: The commit that is currently being checked.
108    will be repeated for each file automatically. If no string is preceding/attached
148 The key can be any name (as long as the syntax is valid), as can the program
149 that is executed. The key is used as the name of the hook for reporting purposes,
152 Whitespace in the key name is OK!
178 * `clang_format`: Run git-clang-format against the commit. The default style is
195 * `jsonlint`: Verify JSON code is sane.
220 Quoting is handled naturally.  i.e. use `"a b c"` to pass an argument with
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
263 executables can be overridden through `[Tool Paths]`.  This is helpful to
296 * Don't worry about namespace collisions.  The `pre-upload.py` script is loaded
297   and exec-ed in its own context.  The only entry-point that matters is `main`.
303 If the return code of a hook is 77, then it is assumed to be a warning.  The
310 * Some checkers operate on the files as they exist in the filesystem.  This is
317   instead of relying on the version that is in $PATH.