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 |
---|---|
2449 | * location to be potentially managed by a version control system. |
2450 | * |
2451 | * @since 3.7.0 |
2452 | * |
2453 | * @param bool $checkout Whether a VCS checkout was discovered at $context |
2454 | * or ABSPATH, or anywhere higher. |
2455 | * @param string $context The filesystem context (a path) against which |
2456 | * filesystem status should be checked. |
2457 | */ |
2458 | return apply_filters( 'automatic_updates_is_vcs_checkout', $checkout, $context ); |
2459 | } |
2460 |
|
2461 | /** |
2462 | * Tests to see if we can and should update a specific item. |
2463 | * |
2464 | * @since 3.7.0 |
2465 | * |
2466 | * @param string $type The type of update being checked: 'core', 'theme', |
2467 | * 'plugin', 'translation'. |