# Version Control Support

**URL:** https://community.kinsta.com/t/version-control-support/172
**Category:** Feature Requests
**Created:** [January 20, 2021, 7:44pm UTC](https://community.kinsta.com/t/version-control-support/172 "2021-01-20T19:44:46Z")
**Posts on this page:** 4
**Page:** 1

<div class="post-metadata">

### Author: ![Juan\_Gongora](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/juan_gongora/32/126_2.png) [@Juan\_Gongora](https://community.kinsta.com/u/Juan_Gongora)
#### Post date: [January 20, 2021, 7:44pm UTC](https://community.kinsta.com/t/version-control-support/172/1 "2021-01-20T19:44:46Z")

</div>

Hi There,

I was wondering if DevKinsta would have any particular issues with creating a git branch for version control locally? Would there be any custom directories/files that are added onto a WordPress environment through this new feature, that would conflict with an already existing repository?

Thanks in advance!

Juan

---

<div class="post-metadata">

### Author: ![shamajay](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/shamajay/32/455_2.png) [@shamajay](https://community.kinsta.com/u/shamajay)
#### Post date: [April 22, 2021, 8:19pm UTC](https://community.kinsta.com/t/version-control-support/172/2 "2021-04-22T20:19:21Z")

</div>

Hi Juan!

Have you tried implementing the use of Git for local version control yet? I’d like to know if it is possible as well without having conflicting directories and files originating from DevKinsta.

Thanks!  
Shama

---

<div class="post-metadata">

### Author: ![Juan\_Gongora](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/juan_gongora/32/126_2.png) [@Juan\_Gongora](https://community.kinsta.com/u/Juan_Gongora)
#### Post date: [April 22, 2021, 8:54pm UTC](https://community.kinsta.com/t/version-control-support/172/3 "2021-04-22T20:54:58Z")

</div>

Hi Sharma,

I did attempt to have the devkinsta environment be remotely linked to a github repo that was cloned to it. It unfortunately did not work as cleanly as I had hoped, and a lot of the configurations that involved the usage of the devkinsta environment on the local machine were broken afterwards.

However, since my original posting I have not retried it, so it’s possible that this could have been fixed since then, with patches and such.

---

<div class="post-metadata">

### Author: ![michael](https://sea2.discourse-cdn.com/flex020/user_avatar/community.kinsta.com/michael/32/31_2.png) [@michael](https://community.kinsta.com/u/michael)
#### Post date: [April 22, 2021, 11:07pm UTC](https://community.kinsta.com/t/version-control-support/172/4 "2021-04-22T23:07:31Z")

</div>

Hey @shamajay ! Thanks for joining us here at DevKinsta! While you could technically do this already by initializing the local directory where the site is located, the push to Kinsta will contain all other git data as well that you probably don’t want pushed. A similiar issue I suppose to [excluding node\_modules someone else posted](https://community.kinsta.com/t/exclude-node-modules-from-import/227).

Thanks for the feature request!
