-
Notifications
You must be signed in to change notification settings - Fork 2
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
Add auto_sync method to plugin #22
Comments
Wouldn't fetch happen first? So some thoughts from my side:
|
without the force option it wouldnt matter - but with the force option order is important - also relative to the the merge/rm steps.
Yep - we need to give some thought about the best syntax for passing an argument - ie force etc. I can write up some recipes for this, to explain diff strategies.
My feeling is that (if its easy/possible) we should try and do things atomically - ie all steps fail if any steps fail in auto_sync. We could have a potentially configurable retry setting.
My head hurts 8/ |
I think fetch --force - just like on the command line is most logical
Agree. Probably less of an issue if we weren't using INI. Dwayne Translate |
Im figuring this is what the scheduler could call.
The default behaviour would be:
Im figuring all but the last step should be configurable - perhaps a syntax like
or
etc
The text was updated successfully, but these errors were encountered: