WP hooks navigation: Home/browse • Actions index • Filters index
To save our bandwidth, we show only a snippet of code around each occurence of the hook. View complete file in SVN (without highlighting).
The best way to understand what a hook does is to look at where it occurs in the source code.
do_action( "hook_name" )apply_filters( "hook_name", "what_to_filter" ).Remember, this hook may occur in more than one file. Moreover, the hook's context may change from version to version.
| Line | Code |
|---|---|
| 166 | * location to be potentially managed by a version control system. |
| 167 | * |
| 168 | * @since 3.7.0 |
| 169 | * |
| 170 | * @param bool $checkout Whether a VCS checkout was discovered at `$context` |
| 171 | * or ABSPATH, or anywhere higher. |
| 172 | * @param string $context The filesystem context (a path) against which |
| 173 | * filesystem status should be checked. |
| 174 | */ |
| 175 | return apply_filters( 'automatic_updates_is_vcs_checkout', $checkout, $context ); |
| 176 | } |
| 177 | |
| 178 | /** |
| 179 | * Tests to see if we can and should update a specific item. |
| 180 | * |
| 181 | * @since 3.7.0 |
| 182 | * |
| 183 | * @global wpdb $wpdb WordPress database abstraction object. |
| 184 | * |