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