6 ms·

I use the ever living hell out of .git/info/exclude. Works great for scripts/Makefiles I only want locally and collaborators wouldn’t care about or be able to u

I use the ever living hell out of .git/info/exclude. Works great for scripts/Makefiles I only want locally and collaborators wouldn’t care about or be able to use.

RSHEPP 3mo ago
Interested in examples of the types of scripts others collaborators wouldn't be able to use? Like scripts for PR workflows?
- junon 3mo ago
  Usually when I'm working in one part of the codebase and I have sample data or something at a specific path on my local machine and Im testing the same thing over and over again will I make a Makefile or something and info/exclude it to help me keep focused. That's one way I use it.
  - bryancoxwell 3mo ago
    Yeah this is pretty much it.
  - tomjakubowski 3mo ago
    I use git worktrees pretty heavily in my own workflows (I worked like an AI agent before AI agents made worktrees cool). I like to track my ephemera/utility scripts in git, so what I do is keep a private ephemera repo for those, and then use `git worktree add` from the collaborative repo to check out the branch I'm working on there into a subdirectory of my ephemera repo. git-home/ company-project/ <-- git repo with main checked out ephemera/ <-- my private repo my-data-script.py work/ <-- gitignored company-project-feature-X/ <-- worktree on feature-X branch company-project-feature-Y/ <-- worktree on feature-Y branch This way, too, I can easily use the same ephemera scripts across multiple branches, or even multiple repos, concurrently.
    - junon 3mo ago
      Oh this is really clever, I'll have to try this. Thank you :)
    - yaskou 3mo ago
      How do you manage the lifecycle of the worktrees in practice? Is it mostly manual git worktree add/remove, or do you use aliases/scripts/some other tools?
digikata 3mo ago
For quite a while, I've have had a shell fcn that will take all the untracked files listed in a git status, and push them to .git/info/exclude. Generally applied after an add+commit of everything I do want to go generally into the repo.

I use the ever living hell out of .git/info/exclude. Works great for scripts/Makefiles I only want locally and collaborators wouldn’t care about or be able to use.

RSHEPP 3mo ago

Interested in examples of the types of scripts others collaborators wouldn't be able to use? Like scripts for PR workflows?

junon 3mo ago
Usually when I'm working in one part of the codebase and I have sample data or something at a specific path on my local machine and Im testing the same thing over and over again will I make a Makefile or something and info/exclude it to help me keep focused. That's one way I use it.
- bryancoxwell 3mo ago
  Yeah this is pretty much it.
- tomjakubowski 3mo ago
  I use git worktrees pretty heavily in my own workflows (I worked like an AI agent before AI agents made worktrees cool). I like to track my ephemera/utility scripts in git, so what I do is keep a private ephemera repo for those, and then use `git worktree add` from the collaborative repo to check out the branch I'm working on there into a subdirectory of my ephemera repo. git-home/ company-project/ <-- git repo with main checked out ephemera/ <-- my private repo my-data-script.py work/ <-- gitignored company-project-feature-X/ <-- worktree on feature-X branch company-project-feature-Y/ <-- worktree on feature-Y branch This way, too, I can easily use the same ephemera scripts across multiple branches, or even multiple repos, concurrently.
  - junon 3mo ago
    Oh this is really clever, I'll have to try this. Thank you :)
  - yaskou 3mo ago
    How do you manage the lifecycle of the worktrees in practice? Is it mostly manual git worktree add/remove, or do you use aliases/scripts/some other tools?

digikata 3mo ago

For quite a while, I've have had a shell fcn that will take all the untracked files listed in a git status, and push them to .git/info/exclude. Generally applied after an add+commit of everything I do want to go generally into the repo.