21
you are viewing a single comment's thread
view the rest of the comments
view the rest of the comments
this post was submitted on 27 Aug 2024
21 points (95.7% liked)
Programming
17314 readers
244 users here now
Welcome to the main community in programming.dev! Feel free to post anything relating to programming here!
Cross posting is strongly encouraged in the instance. If you feel your post or another person's post makes sense in another community cross post into it.
Hope you enjoy the instance!
Rules
Rules
- Follow the programming.dev instance rules
- Keep content related to programming in some way
- If you're posting long videos try to add in some form of tldr for those who don't want to watch videos
Wormhole
Follow the wormhole through a path of communities !webdev@programming.dev
founded 1 year ago
MODERATORS
I haven't seen
git update-index --skip-worktree
mentioned yet. You can read about the motivation for this feature in the git scm docs.I have used it in the past when a professor wanted us to clone repos for assignments that included some opinionated settings for VSCode that I didn't want to use. Skipping the work tree for that directory allowed me to change or delete the config files without git complaining every time I pushed or pulled or whatever, and the changes I made remained local.
You could set up a couple git aliases to "freeze" and "thaw" your config files on the second drive.
@anon2963@infosec.pub
On this same train of thought: there's also git sparse-checkout which uses the skip-worktree bit under the hood, and may have an easier interface. I'm not sure though, I haven't used it yet.