Lines Matching refs:of

29 There are two types of config files:
30 * Repo project-wide settings (e.g. all of AOSP).  These set up defaults for all
35 The merging of these config files control the hooks/checks that get run when
43 * `GLOBAL-PREUPLOAD.cfg`: The top level of the repo checkout.
52 This file is checked in the top of a specific git repository.  Stacking them
79 Hooks are executed in the top directory of the git repository.  All paths should
84 * `REPO_PROJECT`: The name of the project.
88 * `REPO_REMOTE`: The name of the git remote.
90 * `REPO_LREV`: The name of the remote revision, translated to a local tracking
105 * `${PREUPLOAD_FILES}`: List of files to operate on.
106 * `${PREUPLOAD_FILES_PREFIXED}`: A list of files to operate on.
116 * `${REPO_ROOT}`: The absolute path of the root of the repo checkout.
122 Here are some examples of using the placeholders.
138 This section allows for setting options that affect the overall behavior of the
149 that is executed. The key is used as the name of the hook for reporting purposes,
156 You do not need to send stderr to stdout.  The tooling will take care of
170 This section allows for turning on common/builtin hooks.  There are a bunch of
181 * `commit_msg_relnote_field_format`: Check for possible misspellings of the
193 * `pylint`: Alias of `pylint2`.  Will change to `pylint3` by end of 2019.
214 Used to customize the behavior of specific `[Builtin Hooks]`.  Any arguments set
233 default it will call those tools from the user's `$PATH`, but the paths of those
256 # Or paths relative to the top of the git project.
273 If the return code of a hook is 77, then it is assumed to be a warning.  The
284   doing a full checkout of the repo in a temp dir, but this can slow things down
287   instead of relying on the version that is in $PATH.
289   their own list of files like `.cc` and `.py` and `.xml`.