maxyu1115 / maxyu1115/git-backup-sync
When running loadBackup, instead of always stashing, add configurable setting to abort if there are changes
Nobody has claimed this yet.
- Dominant language
- TypeScript
- Stars
- 2
- Forks
- 2
- PR merge metrics
- No merged PRs in 30d
Description
When running loadBackup, currently it always starts off with stashing. We would like to add a configurable setting, to detect if there are any uncommitted changes in your current git repository. If there are, abort the loadBackup. And by creating the setting, the user gets to choose if they always want to stash, or they want the loadBackup to fail in case they accidentally called it.
Contributor guide
No contributing guide indexed for this repository
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 loadBackup entry point and trace the current stash behavior and configuration handling. Add a user-selectable mode for stashing or aborting when the repository has uncommitted changes, then verify both behaviors with a changed working tree.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- git, typescript, vscode
- Domain
- tooling
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100