VisiCut should remember from which git repo the settings were loaded, and regularly check that repo for updates.
Todo: how to present the updates?
Possible three way merge betweeen a) originally loaded, b) user changed, and c) suggested update.
Or only per setting: when reviewing one specific value, visualize in what way it was changed a) by the user, b) on the repo.
VisiCut should remember from which git repo the settings were loaded, and regularly check that repo for updates.
Todo: how to present the updates?
Possible three way merge betweeen a) originally loaded, b) user changed, and c) suggested update.
Or only per setting: when reviewing one specific value, visualize in what way it was changed a) by the user, b) on the repo.