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 |
---|---|
105 | * location to be potentially managed by a version control system. |
106 | * |
107 | * @since 3.7.0 |
108 | * |
109 | * @param bool $checkout Whether a VCS checkout was discovered at $context |
110 | * or ABSPATH, or anywhere higher. |
111 | * @param string $context The filesystem context (a path) against which |
112 | * filesystem status should be checked. |
113 | */ |
114 | return apply_filters( 'automatic_updates_is_vcs_checkout', $checkout, $context ); |
115 | } |
116 |
|
117 | /** |
118 | * Tests to see if we can and should update a specific item. |
119 | * |
120 | * @since 3.7.0 |
121 | * |
122 | * @global wpdb $wpdb WordPress database abstraction object. |
123 | * |