feat: backup the original file before manage it by lazyssh #49
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This was referenced Sep 12, 2025
Closed
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
This PR introduces a backup mechanism for files managed by lazyssh.
Before applying any changes, the original file will be backed up once, ensuring a safe rollback path if needed.
Changes
Motivation
While
lazysshalready maintains rolling backups (up to 10 recent versions), it did not preserve the original unmodified file. This change ensures that users always have a safe restore point to the file’s pristine state, improving reliability and safety.Notes
Original backup is created only once before the first modification.
Existing rolling backup system (last 10 versions) remains unchanged.