WP_Customize_Manager::branching(): bool

784	public function branching() {785 786		/**787		 * Filters whether or not changeset branching is allowed.788		 *789		 * By default in core, when changeset branching is not allowed, changesets will operate790		 * linearly in that only one saved changeset will exist at a time (with a 'draft' or791		 * 'future' status). This makes the Customizer operate in a way that is similar to going to792		 * "edit" to one existing post: all users will be making changes to the same post, and autosave793		 * revisions will be made for that post.794		 *795		 * By contrast, when changeset branching is allowed, then the model is like users going796		 * to "add new" for a page and each user makes changes independently of each other since797		 * they are all operating on their own separate pages, each getting their own separate798		 * initial auto-drafts and then once initially saved, autosave revisions on top of that799		 * user's specific post.800		 *801		 * Since linear changesets are deemed to be more suitable for the majority of WordPress users,802		 * they are the default. For WordPress sites that have heavy site management in the Customizer803		 * by multiple users then branching changesets should be enabled by means of this filter.804		 *805		 * @since 4.9.0806		 *807		 * @param bool                 $allow_branching Whether branching is allowed. If `false`, the default,808		 *                                              then only one saved changeset exists at a time.809		 * @param WP_Customize_Manager $wp_customize    Manager instance.810		 */811		$this->branching = apply_filters( 'customize_changeset_branching', $this->branching, $this );812 813		return $this->branching;814	}