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 |
|---|---|
| 1810 | * location to be potentially managed by a version control system. |
| 1811 | * |
| 1812 | * @since 3.7.0 |
| 1813 | * |
| 1814 | * @param bool $checkout Whether a VCS checkout was discovered at $context |
| 1815 | * or ABSPATH, or anywhere higher. |
| 1816 | * @param string $context The filesystem context (a path) against which |
| 1817 | * filesystem status should be checked. |
| 1818 | */ |
| 1819 | return apply_filters( 'automatic_updates_is_vcs_checkout', $checkout, $context ); |
| 1820 | } |
| 1821 | |
| 1822 | /** |
| 1823 | * Tests to see if we can and should update a specific item. |
| 1824 | * |
| 1825 | * @since 3.7.0 |
| 1826 | * |
| 1827 | * @param string $type The type of update being checked: 'core', 'theme', |
| 1828 | * 'plugin', 'translation'. |