-
Notifications
You must be signed in to change notification settings - Fork 112
handle --force when checking for incorrect password #196
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
Conversation
|
This looks like a good improvement thanks, but I'm getting test failures in cases where a newly-created repository doesn't yet have a HEAD reference:
We will need to find a variant of the dirty files check command that works in this scenario. Note that I moved the duplicated dirty file check command into a reusable function |
8b5acc2 to
49b346a
Compare
compare dirty before and after. see #195 (comment)
PS: switched to the same dirty check we have in run_safety_checks for consistency