# Version Controlling at the Project Scope

**URL:** <https://forum.inductiveautomation.com/t/version-controlling-at-the-project-scope/54546>\
**Category:** Ignition\
**Tags:** ignition81\
**Created:** [December 30, 2021, 4:22pm UTC](https://forum.inductiveautomation.com/t/version-controlling-at-the-project-scope/54546 "2021-12-30T16:22:03Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![dillon](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/dillon/32/81537_2.png) [@dillon](https://forum.inductiveautomation.com/u/dillon)\
**Post date:** [December 30, 2021, 4:22pm UTC](https://forum.inductiveautomation.com/t/version-controlling-at-the-project-scope/54546/1 "2021-12-30T16:22:03Z")

</div>

Hello all,  
I have an idea of having a git repository per project folder (Ignition/data/projects/_NAME_) instead of one repo for the gateway. I am currently trying this methodology and so far so good… The reasoning behind this was to have different project boards in Azure Dev Ops for each respective project.

Is there anyone out there with experience to this sort of idea? Or anyone with general knowledge on how this could be good or potentially bad to do? Any opinions or knowledge welcome 🙂

---

<div class="post-metadata">

**Author:** ![jespinmartin1](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/jespinmartin1/32/57175_2.png) [@jespinmartin1](https://forum.inductiveautomation.com/u/jespinmartin1)\
**Post date:** [December 31, 2021, 4:38pm UTC](https://forum.inductiveautomation.com/t/version-controlling-at-the-project-scope/54546/2 "2021-12-31T16:38:42Z")

</div>

Use Ignition Exchange as private resource and upload projects there