Whenever I commit, I worry that I might have missed the dependency, and I'm looking for the easiest way to test the git tree individually, to ensure that everything in the git index (βdeliveredβ) will actually compile / execute on its own.
My dependencies between files exist on the file system, where I do "git add", so simple compilation and execution tests do not guarantee that everything I checked will be compiled / executed if the tree (or intermediate area) was checked for a clean file the system.
I can have a continuous build, which will be checked after sending, but I prefer not to have any bad commits in the history, which I then have to fix. So I want to create a sandbox that includes tree validation as well as an index / staging area.
One thing I reviewed is to use git stash twice, i.e.:
- Invoke 'git stash' to save files in index
- Somehow get a list of files not tracked, 'git add' all these files, save a new stash
- Delete all previously unverified files
- Restore original stamp
- Now I have to have a clean environment in which there is only code already registered and code in the intermediate area that I can compile and test.
- As soon as you finish, I will return to the file without traces, and then bounce them to leave me in the same position that I was in originally.
(These unsolicited files may be useful, but itβs not necessary what I want to check in the repository - for example, eclipse projects).
I have the feeling that I am reinstalling a simple problem too much.
source share