openclaw/clawhub
1
0
Fork 0
mirror of https://github.com/openclaw/clawhub.git synced 2026-07-21 19:25:25 -04:00
Code Issues 183 Packages Projects Releases 1 Wiki Activity

Feature Request: Add --dry-run flag to update command #65

New Issue
Open
opened 2026-02-15 17:15:27 -05:00 by yindo · 0 comments
yindo commented 2026-02-15 17:15:27 -05:00
Owner
Copy Link
Copy Source

Originally created by @ewimsatt on GitHub (Feb 4, 2026).

Summary

Add a --dry-run flag to the clawhub update command that shows what would be updated without actually performing the updates.

Use Case

When automating skill updates (e.g., via cron jobs or scheduled tasks), it's useful to preview available updates before applying them. This allows for:

  • Logging what updates are available without changing system state
  • Notification workflows that alert users to available updates
  • Review before committing to updates in production environments

Proposed Behavior

clawhub update --all --dry-run

Output would show:

Would update:
  cost-report: 1.0.0 → 1.0.1
  
Already up to date:
  self-reflection: 1.1.1
  opensoul: 1.0.0
  ...

Alternatives Considered

  • Manually checking each skill against the registry (clawhub explore). It works but is tedious for many skills

Thanks for considering!

Originally created by @ewimsatt on GitHub (Feb 4, 2026). ## Summary Add a `--dry-run` flag to the `clawhub update` command that shows what would be updated without actually performing the updates. ## Use Case When automating skill updates (e.g., via cron jobs or scheduled tasks), it's useful to preview available updates before applying them. This allows for: - Logging what updates are available without changing system state - Notification workflows that alert users to available updates - Review before committing to updates in production environments ## Proposed Behavior ```bash clawhub update --all --dry-run ``` Output would show: ``` Would update: cost-report: 1.0.0 → 1.0.1 Already up to date: self-reflection: 1.1.1 opensoul: 1.0.0 ... ``` ## Alternatives Considered - Manually checking each skill against the registry (`clawhub explore`). It works but is tedious for many skills Thanks for considering!
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
bug
pull-request
Mirrored from GitHub Pull Request
No Label
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: openclaw/clawhub#65
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?