Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

hard-reset vs amend during update command #220

Open
neomilium opened this issue Apr 24, 2021 · 0 comments
Open

hard-reset vs amend during update command #220

neomilium opened this issue Apr 24, 2021 · 0 comments

Comments

@neomilium
Copy link
Contributor

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.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

No branches or pull requests

1 participant