Info | ||
---|---|---|
| ||
How to rebase a task to bring in changes from other tasks which have been promoted within the same project, and also from changes in other projects promoted to their mainline, via rebase of the project. This process keeps tasks synchronized with changes made in other project tasks prior to project promotion, and also (following parent project rebase) with changes made in other projects which have been promoted to their mainline. A task becomes diverged from its project when the project content gets updated after the task was initialized. This may happen through other tasks being promoted to the project before the task in question can be promoted, and also through project rebase from its mainline. When task content becomes diverged from its parent project, the task becomes eligible for rebasing from the project, to synchronise its content with the parent branch changes since the task was created. Prerequisites: Create a new concept or Create a new concept based on a template or Create a batch of concepts based on a template or Edit a published concept |
Note | ||
---|---|---|
| ||
Task promotion is not possible whilst a task is diverged, so periodic rebasing is an important aspect of project and task management - ideally as soon as possible following divergence (fewer differences make for simpler content merges). Attempting to promote a task which is diverged (indicated by an active rebase action button for that task) will trigger a Promote Task pop-up notification that the task and project are not synchronized. The only available action on that notification is to return to the task - the promotion request is blocked. |
Excerpt | |||||||||||||||||||||||||||||||||||||||||
---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
|