-
Notifications
You must be signed in to change notification settings - Fork 60
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Add --dry-run Functionality to TwinTrim for Safe Simulated Duplicate Removal #74
Conversation
@adityakalburgi |
ok will share it |
Hi! @Kota-Karthik here is the screenshort how it works |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Make these changes and wait for further review.
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
i have done the required changes
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
I do not see the changes in option seciton in readme yet, kindly implement it.
@techy4shri DONE!! I have added it in option section.. |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Approved! Everything is great! Thank you @adityakalburgi
Hi! @Kota-Karthik can you please explain me what the issue is?.. |
@adityakalburgi go through the changes you made and try to run the project |
This PR introduces a --dry-run option to TwinTrim, allowing users to simulate the duplicate removal process without making any changes. The feature is designed to give users a safe preview of what actions will be taken, ensuring they can confidently proceed with the actual duplicate removal process.
Key Changes:
Added the --dry-run flag to simulate file deletions.
Updated the core logic to handle the dry run mode.
Modified the README to include documentation
resolves issue #58