Currently when you predict like: 'SOME_VAR=$(sbot predict version --verbose)' the predicted version is stored in to the variable. Would be great to have a verbose log of it as well with the --verbose flag.
e.g.:
16:28:21 + sbot update version --verbose
16:28:21 14:28:21 INF updating version...
16:28:21 14:28:21 INF fetching unshallow repository...
16:28:21 14:28:21 WRN ignoring failed unshallow fetch for now, repository might already be complete
16:28:21 14:28:21 INF fetching tags...
16:28:22 [Pipeline] sh
16:28:23 + sbot predict version --verbose
16:28:23 14:28:22 INF getting version...
16:28:23 14:28:22 INF 0.3.0
16:28:23 14:28:22 INF predicting version...
16:28:23 14:28:22 WRN falling back to patch mode
16:28:23 [Pipeline] sh
16:28:23 + sbot get version --verbose
16:28:23 14:28:23 INF getting version...
16:28:23 14:28:23 INF 0.3.0
16:28:23 0.3.0
Currently when you predict like: 'SOME_VAR=$(sbot predict version --verbose)' the predicted version is stored in to the variable. Would be great to have a verbose log of it as well with the --verbose flag.
e.g.:
16:28:21 + sbot update version --verbose 16:28:21 14:28:21 INF updating version... 16:28:21 14:28:21 INF fetching unshallow repository... 16:28:21 14:28:21 WRN ignoring failed unshallow fetch for now, repository might already be complete 16:28:21 14:28:21 INF fetching tags... 16:28:22 [Pipeline] sh 16:28:23 + sbot predict version --verbose 16:28:23 14:28:22 INF getting version... 16:28:23 14:28:22 INF 0.3.0 16:28:23 14:28:22 INF predicting version... 16:28:23 14:28:22 WRN falling back to patch mode 16:28:23 [Pipeline] sh 16:28:23 + sbot get version --verbose 16:28:23 14:28:23 INF getting version... 16:28:23 14:28:23 INF 0.3.0 16:28:23 0.3.0