Revert strategy
Nobody has claimed this yet.
- Dominant language
- Shell
- Stars
- 7.8k
- Forks
- 3.2k
- PR merge metrics
- No merged PRs in 30d
Description
It would be nice to have a strategy to "clean up" once you're all done - to let people try this project out without risk of cluttering their system. Something like this is a simple start, but it would be vastly improved if the script detected *.backup files and restored them to their proper locations, and potentially even deleted the ~/.dotfiles directory
in script/unbootstrap:
#!/usr/bin/env bash
#
# unbootstrap uninstalls things.
cd "$(dirname "$0")/.."
DOTFILES_ROOT=$(pwd)
uninstall_dotfiles () {
info 'uninstalling dotfiles'
for src in $(find "$DOTFILES_ROOT" -maxdepth 2 -name '*.symlink')
do
dst="$HOME/.$(basename "${src%.*}")"
echo "Removing $dst"
rm "$dst"
done
}
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 with script/unbootstrap and trace how the project creates .symlink and *.backup files. Define the cleanup behavior for restoring backups and removing generated dotfiles, then verify it leaves the user's system without clutter after an uninstall.
Written by the indexing model from the issue text.
Assessment
- Tech stack
- shell
- Domain
- cli
- Issue type
- Feature
- Difficulty
- 3/5
- Estimated time
- 1-2 days
- Activity status
- Stale
- Clarity
- Mostly clear
- Newbie friendliness
- 35/100