If you do not need to track these files at all ...
... you can do git ignore .
If you want to track them locally ...
... but don't have them in the remote repo. I can only give you some tips / ideas for a thing I have never tried , but you will probably end up with different repositories and things,> a little disgusting.
I would look at (from, perhaps, to the level of a probably pretty dirty and bad idea):
- Nested Repositories
- Delete when pressed : (Disadvantage: you probably wonβt be able to distinguish correctly, since the stories correspond only to the temporary repository. You could , of course, hack your difference in one way or another, which makes the configuration even more dirty.)
- Steps:
- Before you click the clone repository button in a temporary folder
- Delete your subfolder from the whole story inside the newly created clone (getting a different repository with different hashes commit)
- Click the newly created repository.
- Options: Trigger:
- Options: Delete:
Again: I have not used any of them , but do not know my flaws, traps, etc. , but it seems to me that subtrees are the best solution of the above.
Most of the rest makes me pretty dirty, but at the end of the day , only what works for you is important .
The ship is lousy, but the ship.
... whether in Wasabi
source share