Push content to target branches
You can push any type of object to other target branches, such as a bulk push of all eligible children of a map or a push of a single topic and its content, images, or ditavals.
Authoring:done
. However, your configuration
might be different.Before you push topics, such as the children of a map, consider the implications of having a new instance of that content and your future usage of that content. You should know whether or not you want to create a division between former content and your planned new content or if you want updates to flow to all versions of the object.
If you choose to edit a map child object in only some branches, then that object is forked. With the forked object, you create a new instance of the object in the branches that you selected, and all your changes apply to this new instance. However, the object remains unchanged in the original object for the branches that you did not select. Two instances of the object now exist, and you can choose to either manually update them independently to push updates to all branches or you can auto-update them, which keeps any existing objects at their original state and only updates the new forked object.
When you push an object, one of the following happens:
- If target branches do not already have an instance of the object, they will share the object that you push.
- If target branches have a different instance of the object, that instance will update with the content from the object that you push.
To push content to target branches: