You need a license
usage should just be help (avoid extra step)
connect does not exist (see add and cmd list)
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 learn stow. Hopfully this might help me ? (I don't really need help with git that this sçript look to abstract too much for me.)

[–] ad_on_is@lemm.ee 3 points 2 weeks ago (1 children)

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.

[–] Zykino@programming.dev 1 points 2 weeks ago (1 children)

Apparently stow -t exist too.

[–] ad_on_is@lemm.ee 1 points 2 weeks ago

yes ... I fixed that too, using -t and -d now.

[–] 299792458ms@lemmy.zip 2 points 2 weeks ago

If anyone is looking for alternatives there is Chezmoi, it was worked very well for me.

[–] NostraDavid@programming.dev 1 points 2 weeks ago

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.

I'll be sure to check this out!