robrechtme/loco-cli

Feature request: more granularity in `loco-cli status`

robrechtme opened this issue · 1 comments

robrechtme commented

At the moment, loco-cli status works in both ways:

  • Assets present locally but missing remotely
  • Assets present remotely but missing locally

When using this in CI/CD pipelines this can cause issues. It would be nice to add an extra parameter to differentiate which diff to return, e.g. :
loco-cli status --direction=[remote|local|both]

robrechtme commented

Added in 7360e4c (v1.5.0)