If I get half way through repository analysis and hit an error or a failure I should be able to continue analysis the next time I run the CLI. I'd like a message like this:
$ rulectl start
== WARNING ==
We notice that the last time rulectl was run, analysis didn't complete. Would you like to continue where you left off? (y/n)
If the user says yes to continuing, analysis will skip to where it failed last. If it fails again, let the CLI fail. When the CLI starts again after that failure, the behavior should offer to continue again. If the user says no initially, start analysis as it normally would.
Also, add a flag --continue to be used like $ rulectl start --continue to skip the continue question and auto-continue.
This should be supported on all platforms (Windows, Linux, MacOS).
If I get half way through repository analysis and hit an error or a failure I should be able to continue analysis the next time I run the CLI. I'd like a message like this:
If the user says yes to continuing, analysis will skip to where it failed last. If it fails again, let the CLI fail. When the CLI starts again after that failure, the behavior should offer to continue again. If the user says no initially, start analysis as it normally would.
Also, add a flag
--continueto be used like$ rulectl start --continueto skip the continue question and auto-continue.This should be supported on all platforms (Windows, Linux, MacOS).