Even I'm using msync since months now, I never understand why there is an amend option during update and why there is no hard-reset option ATM.
This is probably due to our workflow, so I will describe how we use msync.
We (@opus-codium) use msync to apply massive modifications on multiple repos based on templates.
When we need to apply templates, we start from the master branch and apply modifications in a specific one, e.g. modulesync. If something goes wrong during the process, we change our modulesync templates or/and config then re-apply it the same way.
Before implementing the --hard-reset option, we executed a script to reset our modulesync branch for the master one.
This workflow allow an idempotent behavior, a thing we like a lot (maybe related to puppet love ;-)).
As I'm currently offer some of my time to contribute to msync, I'm asking me about removing the amend option... so I'm looking for a rock-solid workflow that needs amend option.
Even I'm using
msyncsince months now, I never understand why there is anamendoption duringupdateand why there is nohard-resetoption ATM.This is probably due to our workflow, so I will describe how we use
msync.We (@opus-codium) use
msyncto apply massive modifications on multiple repos based on templates.When we need to apply templates, we start from the
masterbranch and apply modifications in a specific one, e.g.modulesync. If something goes wrong during the process, we change our modulesync templates or/and config then re-apply it the same way.Before implementing the
--hard-resetoption, we executed a script to reset ourmodulesyncbranch for themasterone.This workflow allow an idempotent behavior, a thing we like a lot (maybe related to puppet love ;-)).
As I'm currently offer some of my time to contribute to
msync, I'm asking me about removing theamendoption... so I'm looking for a rock-solid workflow that needsamendoption.