Sign Up to our social questions and Answers Engine to ask questions, answer people’s questions, and connect with other people.
Login to our social questions & Answers Engine to ask questions answer people’s questions & connect with other people.
Lost your password? Please enter your email address. You will receive a link and will create a new password via email.
Please briefly explain why you feel this question should be reported.
Please briefly explain why you feel this answer should be reported.
Please briefly explain why you feel this user should be reported.
I have an eclipse jpa project with some tests that use a dummy h2 database to verify the correct loading of data. No new data is presisted to the dummy db
Every time I run the tests the db is considered modified by GIT. How can I avoid the unnecessary checking in of new versions of the database; it’s my understanding that a binary file will just get completely replaced, unnecessarily inflating my repo.
Use
git update-index --assume-unchangedon the db file after you checkout your working copy / branch. You can also try usinggit update-index --skip-worktree