# Best Practices for SVN/GIT on projects **URL:** \ **Category:** Ignition\ **Created:** [November 25, 2019, 7:16pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-svn-git-on-projects/30218 "2019-11-25T19:16:41Z")\ **Posts on this page:** 1\ **Showing post:** 11
**Author:** ![Kevin.Herron](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/kevin.herron/32/7259_2.png) [@Kevin.Herron](https://forum.inductiveautomation.com/u/Kevin.Herron)\ **Post date:** [December 1, 2021, 6:35pm UTC](https://forum.inductiveautomation.com/t/best-practices-for-svn-git-on-projects/30218/11 "2021-12-01T18:35:39Z")
> [@justin.brzozoski](#): > > I hope that maybe IA can resolve the second and allow Ignition to sync up projects from disk without PNG files, but we’ve gotta leave them in for now. No, we have no intention of doing this. A resource is comprised of everything inside the resource directory. You should ignore _nothing_. We are, however, likely going to stop writing back an "externally modified" entry to the resource upon scanning it and noticing the signature is incorrect. We'll just let it be wrong in the file and the in-memory / UI representation will still indicate there is a mismatch when necessary. --- _[View the full topic](https://forum.inductiveautomation.com/t/best-practices-for-svn-git-on-projects/30218)._