Add switches for `rclone cleanup`
Nobody has claimed this yet.
- Dominant language
- Go
- Stars
- 59.8k
- Forks
- 5.4k
- Avg merge
- 2d 14h
- Merged PRs (30d)
- 48
Description
What is your current rclone version (output from rclone version)?
rclone v1.52.2-198-gaedc8623-fix-4395-list-bwlimit-beta
- os/arch: windows/amd64
- go version: go1.14.4
What problem are you are trying to solve?
rclone cleanup is currently described like this:
Clean up the remote if possible. Empty the trash or delete old file versions
I'd like to run rclone cleanup on a remote to just empty the trash, or just to remove versions history.
How do you think rclone should be changed to solve that?
A solution would be to add a couple of switches, something like this:
rclone cleanup --only-empty-trash
and
rclone cleanup --only-remove-file-versions
Contributor guide
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
Start at the rclone cleanup command entry point and inspect how cleanup capabilities are selected for remotes. Determine how the proposed switches should independently select emptying trash or removing file versions, then verify both modes and their interaction with supported remotes through the existing command tests.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- go
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 4/5
- Estimated time
- 3-5 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100