# Version control / git integration

**URL:** <https://community.cdata.com/t/version-control-git-integration/222>\
**Category:** Ideas\
**Tags:** idea, cdata-arc, version-control, git\
**Created:** [June 27, 2023, 10:07am UTC](https://community.cdata.com/t/version-control-git-integration/222 "2023-06-27T10:07:40Z")\
**Posts on this page:** 2\
**Page:** 1

<div class="post-metadata">

**Author:** ![russell-jerseypost](https://avatars.discourse-cdn.com/v4/letter/r/439d5e/32.png) [@russell-jerseypost](https://community.cdata.com/u/russell-jerseypost)\
**Post date:** [June 27, 2023, 10:07am UTC](https://community.cdata.com/t/version-control-git-integration/222/1 "2023-06-27T10:07:40Z")

</div>

As we make changes to workspaces it is important that we use version control.

We also need to control deployment between test and production cData Arc instances.

It would be good if a Workspace could have an associated git repo (HTTPS or SSH) and implement `git commit` and `git push`. at least.

Ideally `git clone` and `git pull` would be useful too

---

<div class="post-metadata">

**Author:** ![DLB](https://avatars.discourse-cdn.com/v4/letter/d/ecb155/32.png) [@DLB](https://community.cdata.com/u/DLB)\
**Post date:** [December 16, 2025, 1:53pm UTC](https://community.cdata.com/t/version-control-git-integration/222/2 "2025-12-16T13:53:30Z")

</div>

Hello.

I agree on this. But what files should be versionned? Is \*.rsb enough?