Granular selection to copy ignored/untracked files into worktree

[JohannesKlauss]

I'd like to have the possibility to granulary copy ignored/untracked files into new worktrees, i.e. env files. Currently its either copy everything or nothing, but everything copies over caches, build artifacts, etc. which takes time and isn't what I want. Copying nothing an manually copying all the files (and remember which ones per project) is quite tedious.

Is this a feature you'd be interested in?

[sbertix]

Hey 👋
I thought about this further on how to actually implement this, and how would you feel about adding some sort of .gitignore for Supacode (.supaignore 🤔) using the same exact syntax? This would prevent polluting settings and shift per-repo/worktree responsibilities to the actual filesystem (which we definitely need for it to scale better imho)

[JohannesKlauss]

I think this might be interesting, though I wonder if this might pose problems in enterprise-like codebases where you can't just check in a .supaignore file for some reason. I think, simplicity-wise, I would prefer a configuration in the Supacode settings per workspace/repository.

[sbertix]

this might pose problems in enterprise-like codebases where you can't just check in a .supaignore file

It doesn't have to live inside the actual repo, even just inside the Supacode default/per-repo directory works.
e.g., at ~/.supacode/repos/supacode where all my Supacode repo worktrees get created (it's just a regular folder, no committing, no enterprise interference) I could easily have an ignore file. And settings UI could accommodate that as easily, without bloating settings.json (which should most likely be refactor to refer to global stuff only, so we don't have leftovers, etc).

It would also pair much better with #226

[JohannesKlauss]

Good point. Sounds good to me 🙂

[cblakkan]

Related to some kind of .supaignore file it would be cool if there was a file we could check in to the repo that would automatically register as the setup/archive/delete script/entrypoint so every new team member doesn't have to copy paste the script target for that repo manually.