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
In dry-run mode, Knope prints shell commands that would be run, but does not actually run them.
In some cases, the CLI tool that Knope is invoking has its own "dry-run" mode, and it would be useful to run that to validate that the command being run is correct.
...and the resulting command when running knope release --dry-run would be git push -o ci.skip --dry-run, which would be both printed and executed.
One problem with this is that there are probably tools where adding the flag at the end doesn't work, so perhaps there could be a "magic" $dryrun variable to handle more complex cases:
In dry-run mode, Knope prints shell commands that would be run, but does not actually run them.
In some cases, the CLI tool that Knope is invoking has its own "dry-run" mode, and it would be useful to run that to validate that the command being run is correct.
I suggest something like:
...and the resulting command when running
knope release --dry-run
would begit push -o ci.skip --dry-run
, which would be both printed and executed.One problem with this is that there are probably tools where adding the flag at the end doesn't work, so perhaps there could be a "magic"
$dryrun
variable to handle more complex cases:Here,
$dryrun
would be empty unless--dry-run
is passed to Knope, and set to--dry-run
otherwise.The text was updated successfully, but these errors were encountered: