# Module Git - Easy integration of git for your development

**URL:** <https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033>\
**Category:** 3rd Party Modules\
**Tags:** ignition80, perspective, vision, ignition81\
**Created:** [April 4, 2023, 4:32pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033 "2023-04-04T16:32:26Z")\
**Posts on this page:** 20\
**Page:** 3

<div class="post-metadata">

**Author:** ![andrew.brauer](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/andrew.brauer/32/34853_2.png) [@andrew.brauer](https://forum.inductiveautomation.com/u/andrew.brauer)\
**Post date:** [October 23, 2023, 2:16pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/44 "2023-10-23T14:16:29Z")

</div>

It looks like you need to configure your identity in Git. Open a terminal and run this command for your user account. Below is an example script.

```auto
$ git config --global user.name "John Doe"
$ git config --global user.email johndoe@example.com

```

This is important because every Git commit uses this information, and it’s immutably baked into the commits you start creating. I have ran into this before on a new system when I forget to configure my identity in Git. 😉

---

<div class="post-metadata">

**Author:** ![Vakaris\_Urbanavicius](https://avatars.discourse-cdn.com/v4/letter/v/278dde/32.png) [@Vakaris\_Urbanavicius](https://forum.inductiveautomation.com/u/Vakaris_Urbanavicius)\
**Post date:** [November 2, 2023, 1:11pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/45 "2023-11-02T13:11:00Z")

</div>

Using your GitHub PAT instead your password seems to fix this issue

---

<div class="post-metadata">

**Author:** ![Vakaris\_Urbanavicius](https://avatars.discourse-cdn.com/v4/letter/v/278dde/32.png) [@Vakaris\_Urbanavicius](https://forum.inductiveautomation.com/u/Vakaris_Urbanavicius)\
**Post date:** [November 2, 2023, 1:14pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/46 "2023-11-02T13:14:07Z")

</div>

Should be possible to resolve this issue temporarily by committing and pushing using cmd.

---

<div class="post-metadata">

**Author:** ![ron.sherrod](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ron.sherrod/32/27007_2.png) [@ron.sherrod](https://forum.inductiveautomation.com/u/ron.sherrod)\
**Post date:** [November 20, 2023, 8:06pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/47 "2023-11-20T20:06:05Z")

</div>

@e.sagnelonge if i pull from the remote repo onto a new host how are the changes implemented in the project?

---

<div class="post-metadata">

**Author:** ![ron.sherrod](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ron.sherrod/32/27007_2.png) [@ron.sherrod](https://forum.inductiveautomation.com/u/ron.sherrod)\
**Post date:** [November 21, 2023, 2:12am UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/48 "2023-11-21T02:12:30Z")

</div>

I am seeing that there is a delay in the gateway being updated with the changes

---

<div class="post-metadata">

**Author:** ![pturmel](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/pturmel/32/3295_2.png) [@pturmel](https://forum.inductiveautomation.com/u/pturmel)\
**Post date:** [November 21, 2023, 12:31pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/49 "2023-11-21T12:31:48Z")

</div>

The default scan interval for such changes is five minutes. That can be configured (I don't have it handy), or in later Ignition versions, can be triggered by a system call.

---

<div class="post-metadata">

**Author:** ![ron.sherrod](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ron.sherrod/32/27007_2.png) [@ron.sherrod](https://forum.inductiveautomation.com/u/ron.sherrod)\
**Post date:** [November 21, 2023, 1:32pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/50 "2023-11-21T13:32:04Z")

</div>

Thank you! When pulling from git into the project repo how have you avoided manually git forcing a merge?

---

<div class="post-metadata">

**Author:** ![Tim\_Carlton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim_carlton/32/52835_2.png) [@Tim\_Carlton](https://forum.inductiveautomation.com/u/Tim_Carlton)\
**Post date:** [November 21, 2023, 4:57pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/51 "2023-11-21T16:57:31Z")

</div>

I am not sure I understand the question.  
My understanding of the terminology is:  
git is the technology for distributed version control.  
A repo is a single unit of controlled artifacts (a folder and all of the code under it, except what is excluded by .gitignore).  
There is a repo in your `Ignition/data/projects/<projectName>` folder. It is hidden and is called `.git`.  
Most likely there is another copy of the repo somewhere else. gitHub, gitLabs, DevOps, gitea are all examples. By convention, this repo is called `remote/origin` and is (by convention) the single source of truth.  
There are other copies of the repo in the distributed environment. Likely one on every development machine. Those would be `remote/<something>`.  
You would pull a repo from any remote machine. For your sanity you would agree that you would only pull from `remote/origin`. You could push a repo to any machine. Again, for the sanity of everyone involved you would only push to `remote/origin`.

There are multiple branches in a repo. By convention, the source of truth for production deployment is `main` or `master`. Development and experiments are done on other branches.

If you pull from a remote machine, git will require a merge only if there are changes to the local repo and the remote repo on the checked out branch.

Given this understanding, avoiding a merge involves using branches.

When are you seeing git force a merge?

---

<div class="post-metadata">

**Author:** ![ron.sherrod](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/ron.sherrod/32/27007_2.png) [@ron.sherrod](https://forum.inductiveautomation.com/u/ron.sherrod)\
**Post date:** [November 21, 2023, 5:19pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/52 "2023-11-21T17:19:23Z")

</div>

I instantiate a new project in the gateway. I then connect them associate that project with a remote repo in Github using git module on a local machine. I open that project in the designer and pull from `remote-origin` . The pull occurs successfully but gets stuck in a merging state and therefore does not update the project. So i use git commands in terminal to force the pull and update the local machine's repo.

I need to add I am not using docker at all for project deployment. I am trying to leverage git across a corporate ecosystem of ignition instances so I can meet 21 CFR requirements in a more automated fashion.

---

<div class="post-metadata">

**Author:** ![Tim\_Carlton](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/tim_carlton/32/52835_2.png) [@Tim\_Carlton](https://forum.inductiveautomation.com/u/Tim_Carlton)\
**Post date:** [November 21, 2023, 5:25pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/53 "2023-11-21T17:25:16Z")

</div>

I think I remember cloning the repo locally the first time rather than pulling.

---

<div class="post-metadata">

**Author:** ![nellis1](https://avatars.discourse-cdn.com/v4/letter/n/0ea827/32.png) [@nellis1](https://forum.inductiveautomation.com/u/nellis1)\
**Post date:** [January 9, 2024, 7:38pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/54 "2024-01-09T19:38:36Z")

</div>

Just wanted to say thank you for making this a publically available tool. I know that this will help keep me and my team up to the ever increasing standards of our industry.

---

<div class="post-metadata">

**Author:** ![Gonzalo\_Emanuel\_Orte](https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/32.png) [@Gonzalo\_Emanuel\_Orte](https://forum.inductiveautomation.com/u/Gonzalo_Emanuel_Orte)\
**Post date:** [January 22, 2024, 5:20pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/55 "2024-01-22T17:20:52Z")

</div>

Hi, first of all, thank you for developing this module; it has been very useful to me.  
Have you considered creating and associating users through scripting?

---

<div class="post-metadata">

**Author:** ![msteele](https://sea1.discourse-cdn.com/inductiveautomation/user_avatar/forum.inductiveautomation.com/msteele/32/77889_2.png) [@msteele](https://forum.inductiveautomation.com/u/msteele)\
**Post date:** [January 22, 2024, 6:52pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/56 "2024-01-22T18:52:58Z")

</div>

Not directly related to the 3rd party git module, but IA staff released some resources for using git on this thread: [Guide for Version Control with Ignition](https://forum.inductiveautomation.com/t/guide-for-version-control-with-ignition/84004/1)

We're currently testing a workflow where our repo root is at the /data folder (gwbk) and devs interact with a local container gateway and monitor/manage commits via VSCode/VSCodium opened to that folder (we also have a UI developer who mostly uses VS Code for editing CSS more than editing in Ignition Designer).

---

<div class="post-metadata">

**Author:** ![M.O](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@M.O](https://forum.inductiveautomation.com/u/M.O)\
**Post date:** [April 4, 2024, 4:00pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/57 "2024-04-04T16:00:55Z")

</div>

Hi All, wondering if anyone else has run into this issue when connecting to GitHub using SSH. Commits are successful, but when I attempt a "push", I get the following error:  
 ![Ignition Error](https://us1.discourse-cdn.com/inductiveautomation/original/3X/9/0/9081dd1aadda12424c95725e908eaca5d751ec88.png)

I have the SSH URI set up for the project:  
[git@github.com](mailto:git@github.com):[companyName]/[repository].git

And I have added my user to the project using an SSH key. I also have the SSH key properly set up in my GitHub account settings and allowed SSO for the SSH key  
 ![IgnitionUser](https://us1.discourse-cdn.com/inductiveautomation/original/3X/4/1/418ecfeaac828dcde19a422e00f4af6d92fcd45c.png)

Here is the full detail of the error:  
[IgnitionError.txt](https://forum.inductiveautomation.com/uploads/short-url/kJ7skKmEldN7pw97IVLlMEdDlqp.txt) (8.6 KB)

Also, our Ignition environment sits on a shared server, not on my local machine. I've made sure to generate my /.ssh files on the server's C drive in case that was the issue, but it doesn't appear so.

EDIT: I've replicated my environment on my local PC and everything works great. So my question is, if we are referring to a shared server instance of Ignition, is there a way to make sure the tool refers to the correct C:\Users\user.ssh\ location? The project on the remote server sits on a different drive, not the C drive.

EDIT2: I was not able to resolve issues with SSH, but I was able to set up a PAT instead to log in

---

<div class="post-metadata">

**Author:** ![jjgomez](https://avatars.discourse-cdn.com/v4/letter/j/59ef9b/32.png) [@jjgomez](https://forum.inductiveautomation.com/u/jjgomez)\
**Post date:** [April 16, 2024, 5:49pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/58 "2024-04-16T17:49:59Z")

</div>

Hi. is anyone having problems where the commit popup is empty after changes?

 ![image](https://us1.discourse-cdn.com/inductiveautomation/original/3X/7/d/7d82ee2097a784da231887445880d96778d22d58.png)

---

<div class="post-metadata">

**Author:** ![Gonzalo\_Emanuel\_Orte](https://avatars.discourse-cdn.com/v4/letter/g/ac91a4/32.png) [@Gonzalo\_Emanuel\_Orte](https://forum.inductiveautomation.com/u/Gonzalo_Emanuel_Orte)\
**Post date:** [April 16, 2024, 6:45pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/59 "2024-04-16T18:45:05Z")

</div>

Hi, I have that problem frequently, the only solution I found was to commit with Git directly and then close it, after that the problem was resolved (momentarily).

---

<div class="post-metadata">

**Author:** ![M.O](https://avatars.discourse-cdn.com/v4/letter/m/a183cd/32.png) [@M.O](https://forum.inductiveautomation.com/u/M.O)\
**Post date:** [June 6, 2024, 1:35pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/60 "2024-06-06T13:35:11Z")

</div>

@e.sagnelonge Have there been any requests for an option to disable the commit popup when saving? In our development environment we do a lot of frequent saves, so it would be valuable to only allow manual commits instead of getting the commit popup on each save.

---

<div class="post-metadata">

**Author:** ![Mehdi\_MECHEDAL](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mehdi\_MECHEDAL](https://forum.inductiveautomation.com/u/Mehdi_MECHEDAL)\
**Post date:** [July 11, 2024, 9:14am UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/61 "2024-07-11T09:14:19Z")

</div>

I have installed the module on Ignition Edge but it does not work, i got the following message:

 ![Screenshot 2024-07-11 105829](https://us1.discourse-cdn.com/inductiveautomation/original/3X/5/c/5cdbbc9f500663ec11a9064a4d162b21c10bc2d0.jpeg)

Note that my Edge Gateway has a valid License.

---

<div class="post-metadata">

**Author:** ![Mehdi\_MECHEDAL](https://avatars.discourse-cdn.com/v4/letter/m/58956e/32.png) [@Mehdi\_MECHEDAL](https://forum.inductiveautomation.com/u/Mehdi_MECHEDAL)\
**Post date:** [July 11, 2024, 11:34am UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/62 "2024-07-11T11:34:21Z")

</div>

I found the answer: not allowed, by IA policy. The only third party that has Edge support is Cirrus Link.

> [@Edge Compatibility](https://forum.inductiveautomation.com/t/edge-compatibility/92710):
>
> Is there a documented way to make a module compatible with Edge? I have combed through the SDK and javadocs and am not finding any obvious way to do it.

---

<div class="post-metadata">

**Author:** ![Aaron\_Murdock](https://avatars.discourse-cdn.com/v4/letter/a/6a8cbe/32.png) [@Aaron\_Murdock](https://forum.inductiveautomation.com/u/Aaron_Murdock)\
**Post date:** [July 12, 2024, 8:30pm UTC](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033/63 "2024-07-12T20:30:32Z")

</div>

I am running into an issue where the git push/pull connection fails. The VM we have running Ignition sits behind a proxy server. Is there a way to specify proxy settings to reach the remote repository (gitlab)?

[Previous page](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033.md?page=2)

[Next page](https://forum.inductiveautomation.com/t/module-git-easy-integration-of-git-for-your-development/72033.md?page=4)
