Reputation: 301
My environment is like this: A dev computer that makes changes to the repository and publishes the repo after commits.
Test box: where the repo is cloned. When running dotnet build it creates files that get attached to the repo. Don't wan this test box to track files and just want to run git pull to get changes without it accounting for the compiled dll's that is created when the project is run.
besides git reset --hard which sometimes fails because of locked files. Just want git to fetch the files from origin and overwrite if necessary files which it feels like tracking.
Upvotes: 0
Views: 47
Reputation: 1463
You might try putting the names of the files you don't want tracked in the .gitignore file on the test box. .gitignore lives in the directory at the top of your source, (where the .git dir lives).
Here are a few examples of files often put in the .gitignore file:
*.hex
*.bin
*.cyacd
*.rgn
*.dlx
Upvotes: 1
Reputation: 11558
There are probably a number of solutions here but the one that sticks out the most to me is that you shouldn't be tracking folders that produce builds and other build artifacts. I suggest you add an appropriate .gitignore
file to stop git from caring about build artifacts.
Here is an example .gitignore
file for most common .NET projects.
Upvotes: 1