# Version Controlling Steps with Resource.json Files

**URL:** <https://forum.inductiveautomation.com/t/version-controlling-steps-with-resource-json-files/117920>\
**Category:** Ignition\
**Tags:** ignition83\
**Created:** [November 20, 2026, 2:36pm UTC](https://forum.inductiveautomation.com/t/version-controlling-steps-with-resource-json-files/117920 "2026-11-20T14:36:40Z")\
**Posts on this page:** 3\
**Page:** 1

<div class="post-metadata">

**Author:** ![Alexander\_Waizmann](https://avatars.discourse-cdn.com/v4/letter/a/839c29/32.png) [@Alexander\_Waizmann](https://forum.inductiveautomation.com/u/Alexander_Waizmann)\
**Post date:** [November 20, 2026, 2:36pm UTC](https://forum.inductiveautomation.com/t/version-controlling-steps-with-resource-json-files/117920/1 "2026-11-20T14:36:40Z")

</div>

After reading some of the other posts on this forum about the resource.json files contained within an Ignition project, I was wondering what the proper way to version control these items would be.

After pulling the most up-to-date version of a project on the gateway, should you enter the designer to "save", which could update the resource.json files? Or are they not updated when saving a project with no changes made directly in the designer?

The posts I've read give me some assurance that the _presence_ of resource.json files is incredibly important, but how you would go about controlling them is a bit confusing.

---

<div class="post-metadata">

**Author:** ![Noah\_Burnette](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/noah_burnette/32/83777_2.png) [@Noah\_Burnette](https://forum.inductiveautomation.com/u/Noah_Burnette)\
**Post date:** [November 20, 2026, 5:54pm UTC](https://forum.inductiveautomation.com/t/version-controlling-steps-with-resource-json-files/117920/2 "2026-11-20T17:54:56Z")

</div>

Hey Alexander,

In 8.3 the issues for `resource.json` are greatly reduced. 8.3 is a lot more lenient on restoring the `resource.json`. You won't get the churn like you used to with 8.1. You can safely restore **tracked** `resource.json` without issue.

I only commit a `resource.json` if I made changes to the resource e.g. `code.py`, `view.json`, `config.json`. For newly untracked resources, you **must** commit `resource.json` or else you'll have a bunch of problems as mentioned across different posts on the forum.

Hope this helps!

---

<div class="post-metadata">

**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:** [November 20, 2026, 9:35pm UTC](https://forum.inductiveautomation.com/t/version-controlling-steps-with-resource-json-files/117920/3 "2026-11-20T21:35:48Z")

</div>

> [@Noah\_Burnette](#):
>
> You can safely restore **tracked** `resource.json` without issue.

Note that, depending on the resource type you're committing, there can be structurally significant changes in the `resource.json` attributes section. Make sure to double check both versions or you're going to have a bad time.

> [@Noah\_Burnette](#):
>
> In 8.3 the issues for `resource.json` are greatly reduced.

The gist of this is that as of 8.3 we're no longer writing _back_ an updated `resource.json` file when we detect that the "last modification" attributes changed out from under us. Longer term, we're very interested in a more cohesive solution to separate that tracking metadata out of the actual resource signature, but it's not going to change in 8.3 or 2027 at least.
