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
Hipcheck requires some files to be present / findable by it in order to run. Currently, these are checked at the start of running Hipcheck, but it checks them one by one and doesn't give a convenient way to check the full readiness of Hipcheck to execute. While this can also be improved in the hc check flow, it would be nice to have a separate command that checks Hipcheck's readiness to run by looking for configuration, data files, and a place to put clones, and reports everything it finds. This would also help people to debug if they feel like Hipcheck found inferred the wrong location.
The text was updated successfully, but these errors were encountered:
This could also support the deprecation of the --print-config, --print-data, --print-home flag commands, which is ideal. I don't really like that we've made it so some flags run commands instead.
The hc doctor command should also give instructions for fixing any problems it identifies, like missing helper scripts or lack of configuration files. This would also help ease the workflow of people installing just the Hipcheck binary through something like cargo binstall or an Axo install script in the future.
Hipcheck requires some files to be present / findable by it in order to run. Currently, these are checked at the start of running Hipcheck, but it checks them one by one and doesn't give a convenient way to check the full readiness of Hipcheck to execute. While this can also be improved in the
hc check
flow, it would be nice to have a separate command that checks Hipcheck's readiness to run by looking for configuration, data files, and a place to put clones, and reports everything it finds. This would also help people to debug if they feel like Hipcheck found inferred the wrong location.The text was updated successfully, but these errors were encountered: