You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
Note: Move this and the related tasks to new zeebe modeler repository. Atm it is located on this repository.
In #1031 we were able to create a new Zeebe Modeler prototype as fork of the newly camunda-modeler architecture. To create a stable modeler, there are couple of things to do:
Discuss: Implement commit message guideline to label commits inside camunda-modeler as unrelated for Zeebe Modeler?
Nice to have
sync-task: Make it more modular and configurable (e.g. handling merge commit message, upstream name, upstream branch, merge vs. rebase etc.), yargs (sync-fork#L291)
sync-task: Get rid of simple-git dependency and built it via execa? (sync-fork#L8)
sync-task: Move to own repo ?
[1] After excluding unrelated files, recheck existing merge conflicts. If no other exists, run git commit, otherwise offer auto merge tool for merge conflicts (sync-fork#L234)
The text was updated successfully, but these errors were encountered:
Note: Move this and the related tasks to new zeebe modeler repository. Atm it is located on this repository.
In #1031 we were able to create a new Zeebe Modeler prototype as fork of the newly
camunda-modeler
architecture. To create a stable modeler, there are couple of things to do:Overall tasks
Zeebe Tab
Synchronization task
camunda-modeler
as unrelated for Zeebe Modeler?Nice to have
yargs
(sync-fork#L291)execa
? (sync-fork#L8)[1] After excluding unrelated files, recheck existing merge conflicts. If no other exists, run git commit, otherwise offer auto merge tool for merge conflicts (sync-fork#L234)
The text was updated successfully, but these errors were encountered: