admin media delete-past-remote-media has confusing time specifiers #1134
Labels
No labels
Bug
Cherry-picking
Database
Dependencies
Dependencies/Renovate
Difficulty
Easy
Difficulty
Hard
Difficulty
Medium
Documentation
Enhancement
Good first issue
Help wanted
Inherited
Matrix/Administration
Matrix/Appservices
Matrix/Auth
Matrix/Client
Matrix/Core
Matrix/Federation
Matrix/Hydra
Matrix/MSC
Matrix/Media
Meta
Meta/CI
Meta/Packaging
Priority
Blocking
Priority
High
Priority
Low
Security
Status/Blocked
Status
Confirmed
Status
Duplicate
Status
Invalid
Status
Needs Investigation
To-Merge
Wont fix
old/ci/cd
old/rust
No milestone
No project
No assignees
2 participants
Notifications
Due date
No due date set.
Dependencies
No dependencies set.
Reference
continuwuation/continuwuity#1134
Loading…
Add table
Add a link
Reference in a new issue
No description provided.
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?
--before,--after,--newer-than,--older-thanare all ambiguous and continue to cause issues with trying to grasp how this command works. Rephrasing the arguments so that they are less ambiguous and easier to understand a glance will go a long way to making sure people don't lose data.Please suggest the arguments you think would best make sense for this command because it seems nobody can quite get it right.
I think both variants are fine, as long as the doc comments state clearly what each do.
As mentioned in the chat, I read
--beforeand--older-thanas deleting all files created before and up to that given point in time. And--after/--newer-thanas delete all files created at the given point in time and later, up until right now.Another way, could be to have a
--spanargument, or similar, where you specify an inclusive time range to match against. But I guess that could be confusing as well.admin media delete-past-remote-media#1136