Stow has been pretty amazing for my dotfiles repo. Being able to just stow adapt <folder> and git reset --hard to overwrite an existing config on a new machine is just so nice.
You can git clone <REPO> <DEST FOLDER>, no need to cd
maybeCreateDir is not used each time, there are some mkdir
"changes" is not a helpfull commit message. Accept an optional argument string and {MESSAGE:=change}
Accept a different repo path
set -euxo pipefail at the start of the script if you want to exit at any error. Some sort of bash strict mode
shellcheck does not like iterating over ls's output
I'm too lazy to open issues/PR for all that, and I still need to learnstow. Hopfully this might help me ? (I don't really need help with git that this sçript look to abstract too much for me.)
p3x.de
Stow has been pretty amazing for my
dotfilesrepo. Being able to juststow adapt <folder>andgit reset --hardto overwrite an existing config on a new machine is just so nice.I'll be sure to check this out!
usageshould just behelp(avoid extra step)connectdoes not exist (seeaddand cmd list)git clone <REPO> <DEST FOLDER>, no need tocdmaybeCreateDiris not used each time, there are somemkdir{MESSAGE:=change}set -euxo pipefailat the start of the script if you want to exit at any error. Some sort of bash strict models's outputI'm too lazy to open issues/PR for all that, and I still need to learn
stow. Hopfully this might help me ? (I don't really need help withgitthat this sçript look to abstract too much for me.)oh hey.. thx for the input... just did some refactoring... never realized there was also a
git -C workdir <cmd>since I never use it.Apparently
stow -texist too.yes ... I fixed that too, using -t and -d now.
If anyone is looking for alternatives there is Chezmoi, it was worked very well for me.