renku show (sub)commands are currently not implemented with the new database backend and should be reimplemented.
The main command that is important is renku show outputs, which is used by the pre-commit hook to check if any generated output files have been modified by the user.
renku show inputs is second priority, with renku show siblings being lowest priority.
The --revision flag for these commands doesn't make sense anymore. It never shows the status at a revision, instead if would just limit the paths argument to paths touched in commits from revision..HEAD, which still just looking at the metadata in HEAD. So I think this can be left out.
renku show
(sub)commands are currently not implemented with the new database backend and should be reimplemented.The main command that is important is
renku show outputs
, which is used by the pre-commit hook to check if any generated output files have been modified by the user.renku show inputs
is second priority, withrenku show siblings
being lowest priority.The
--revision
flag for these commands doesn't make sense anymore. It never shows the status at a revision, instead if would just limit thepaths
argument to paths touched in commits from revision..HEAD, which still just looking at the metadata in HEAD. So I think this can be left out.