# Project Library script version control **URL:** \ **Category:** Ignition\ **Tags:** ignition80\ **Created:** [June 2, 2020, 3:55pm UTC](https://forum.inductiveautomation.com/t/project-library-script-version-control/35262 "2020-06-02T15:55:02Z")\ **Posts on this page:** 1\ **Showing post:** 7
**Author:** ![joseph.burns](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/joseph.burns/32/61584_2.png) [@joseph.burns](https://forum.inductiveautomation.com/u/joseph.burns)\ **Post date:** [May 10, 2021, 4:25pm UTC](https://forum.inductiveautomation.com/t/project-library-script-version-control/35262/7 "2021-05-10T16:25:30Z")
Yup that works most of the time if you use a single gateway for development. If you develop on multiple gateways, you'll still run into problems though. > [@Resource.json and git](http://forum.inductiveautomation.com/t/resource-json-and-git/38615): > > We’ve been having some strange problems with how the resource.json files get handled when Ignition meets git. The resource.json files seem to update themselves after they are checked in or out. I can do a git reset --hard to set everything back to the HEAD, run a git status, and see that everything is clean. If I wait a few seconds and run git status again, all of my projects’ resource.json files have been modified. When I do a git diff to see what changed, I see that the lastModificaitonSig… --- _[View the full topic](https://forum.inductiveautomation.com/t/project-library-script-version-control/35262)._