# Using Git with Ignition projects **URL:** \ **Category:** Ignition\ **Created:** [June 7, 2022, 11:44pm UTC](https://forum.inductiveautomation.com/t/using-git-with-ignition-projects/60475 "2022-06-07T23:44:47Z")\ **Posts on this page:** 1\ **Showing post:** 2
**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 8, 2022, 12:07am UTC](https://forum.inductiveautomation.com/t/using-git-with-ignition-projects/60475/2 "2022-06-08T00:07:48Z")
Some information, and a not-that-great workaround in this thread: > [@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): > > My colleagues and I try to follow a pretty normal git development flow: we implement things on temporary branches and do peer-reviewed pull requests to merge those into a main “develop” branch. And after some period of testing and vetting, the “develop” branch is then pulled into a “production” branch. We still have to be cautious and avoid more than one of us working on the same binary file at the same time, but we’ve been able to work on the same view or script and git was able to merge chang… --- _[View the full topic](https://forum.inductiveautomation.com/t/using-git-with-ignition-projects/60475)._