Skip to content
This repository has been archived by the owner on Jul 1, 2022. It is now read-only.

Option to ignore dirty repo #25

Open
xendk opened this issue Oct 22, 2014 · 2 comments
Open

Option to ignore dirty repo #25

xendk opened this issue Oct 22, 2014 · 2 comments

Comments

@xendk
Copy link
Member

xendk commented Oct 22, 2014

Would be handy with a switch to force the deployment even if the deployed site isn't clean. But that would require ability to display the changes, and more interactivity. Something to think about.

@kasperg
Copy link
Member

kasperg commented Oct 23, 2014

How would this be different from --insanity apart from displaying changes?

@xendk
Copy link
Member Author

xendk commented Oct 23, 2014

Apart from the fact that I'd totally forgotten --insanity? Not much...

I was actually thinking of taking it a step further. --insanity just tries running anyway, I was thinking of running git --reset hard, as it then has a less chance of failing (git will bomb out if one of the files it's trying to update is changed).

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Development

No branches or pull requests

2 participants