# Resource.json and git **URL:** \ **Category:** Ignition\ **Tags:** ignition80, perspective, scripting\ **Created:** [September 11, 2020, 8:35pm UTC](https://forum.inductiveautomation.com/t/resource-json-and-git/38615 "2020-09-11T20:35:28Z")\ **Posts on this page:** 1\ **Showing post:** 41
**Author:** ![paul-griffith](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/paul-griffith/32/37249_2.png) [@paul-griffith](https://forum.inductiveautomation.com/u/paul-griffith)\ **Post date:** [June 17, 2022, 4:53pm UTC](https://forum.inductiveautomation.com/t/resource-json-and-git/38615/41 "2022-06-17T16:53:20Z")
There’s a lot of words in this thread - can you be more specific about _which_ problem you’re facing? The nature of the `resource.json` file is unlikely to change in 8.1, but _is_ likely to change in 8.2. If you’re adventurous, I reproduced the signature calculation in standalone code here, which you could use to generate valid signature calculations for filesystem modifications: [What's your method for resolving resource.json git conflicts?](https://forum.inductiveautomation.com/t/whats-your-method-for-resolving-resource-json-git-conflicts/60096) Or there’s an approach documented [here](https://forum.inductiveautomation.com/t/using-git-with-ignition-projects/60475/4) about basically ignoring the resource.json files entirely. --- _[View the full topic](https://forum.inductiveautomation.com/t/resource-json-and-git/38615)._