You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
I'm wondering if you would accept a change that checked if we were inside a git repo, and if so refuse to update the file if it's dirty or not checked in (the idea being that this is a safer mode of operation). I might try to implement this if you can give me an idea of the design that you'd accept, if you need backwards compatibility or if the default can change, Etc
The text was updated successfully, but these errors were encountered:
If you want to keep tests pass for every commit, expect-test necessarily has to be able to update dirty files as the changes that made the file containing the test dirty, likely caused the expected test result to change.
I'm wondering if you would accept a change that checked if we were inside a git repo, and if so refuse to update the file if it's dirty or not checked in (the idea being that this is a safer mode of operation). I might try to implement this if you can give me an idea of the design that you'd accept, if you need backwards compatibility or if the default can change, Etc
The text was updated successfully, but these errors were encountered: