WP_Customize_Manager::branching(): bool

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