this post was submitted on 08 Dec 2024
19 points (88.0% liked)

Linux

5491 readers
556 users here now

A community for everything relating to the linux operating system

Also check out !linux_memes@programming.dev

Original icon base courtesy of lewing@isc.tamu.edu and The GIMP

founded 2 years ago
MODERATORS
you are viewing a single comment's thread
view the rest of the comments
[–] Zykino@programming.dev 4 points 2 weeks ago (1 children)
  1. You need a license
  2. usage should just be help (avoid extra step)
  3. connect does not exist (see add and cmd list)
  4. You can git clone <REPO> <DEST FOLDER>, no need to cd
  5. maybeCreateDir is not used each time, there are some mkdir
  6. "changes" is not a helpfull commit message. Accept an optional argument string and {MESSAGE:=change}
  7. Accept a different repo path
  8. set -euxo pipefail at the start of the script if you want to exit at any error. Some sort of bash strict mode
  9. 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.