Cannot commit changes to git

Hello Shawn,

Thank you for the clear description, and sorry for the trouble.

When you click Commit, PowerShell Universal stages the selected files, commits them, then syncs with your remote as your Git settings define (a pull, unless the sync is set to push only, then a push), and the page only moves on once those steps return. To find which step stops on your server, could you send us the following:

1. Click Commit once more, wait a few minutes, then refresh the page and tell us whether the files you tried to commit are still listed on the commit page. That helps us tell whether a local commit was made; it does not show whether the sync with your remote worked. Then open /admin/support on your server and click Support Package, and attach the zip. It contains the server logs and notifications, which show whether a Git error or timeout was recorded during the attempt.

2. Whether External Git Client is turned on: on the Settings tab of the Git page (/admin/git/settings), click the edit button of the repository in use; the checkbox is in that dialog. If the row has no edit button, just tell us so. The setting is described here: https://docs.devolutions.net/powershell-universal/config/git/#external-git-client

3. Roughly how many files the commit page lists under Changes.

Best regards,

Michel

Hello @Michel Audi ,

Should I open a case with Devolutions to submit the zip file? I don't want to attach it here in the public forum.

Hello Shawn,

Thank you for checking before posting it. You are right to keep the zip off this topic, as it is public. There is no need to open a new case. Your topic already has a support case on our side, number 00133910.

You can send the zip privately in either of these two ways, then reply here so I know it is on its way.

1. As a private message to me on the forum, with the zip attached.

2. By email to service@devolutions.net, with the case number 00133910 in the subject.

If you have not taken the Support Package yet, click Commit once more, wait a few minutes and refresh the page first, then download it from /admin/support, so the log covers the attempt.

The other three answers can go here or with the zip.

1. Whether the files you tried to commit were still listed under Changes after that refresh.

2. Whether External Git Client is turned on, in the edit dialog of the repository on the Settings tab of the Git page. The setting is described on this page.

https://docs.devolutions.net/powershell-universal/config/git/#external-git-client

3. Roughly how many files the commit page lists under Changes.

If the zip is too large to attach, tell me and I will send you a private upload link.

Best regards,

Michel

1. Files are still listed on commit page after refreshing, as though the commit never happened.

2. External Git is enabled

3. One file

I'll send the zip file shortly.

I cannot send the zip using any method. The size is over 100mb. The forum limits to 25mb, and email limits to 35mb.

Hello Shawn,

Thank you for the three answers. The file is still listed as uncommitted after the refresh, so the commit did not clear it.

Here is the private upload link I promised for the Support Package.

https://devolutions.sharepoint.com/:f:/s/SessionRecordings/IgDtrKb7wWB3SpRgQsXmY_UpAYB9UfA8ORs2Ml7C7tRrBfQ?e=c8jwYs

It opens only for your email address. It asks for that address and sends a code to it to confirm it. If it refuses your address, send me a private message on the forum rather than posting the address here.

Before you upload, click Commit once more, wait a few minutes and refresh the page, so the log covers that attempt. Then upload either of these.

1. A new Support Package from /admin/support.

2. Or, if you prefer a single file, only the system log of that day. By default it is in %ProgramData%\PowerShellUniversal\Logs\System, unless the system log path was changed in your settings, which this page describes. Its name is systemLog followed by the date, for example systemLog20261103.txt for November 3.

https://docs.devolutions.net/powershell-universal/development/logging

If a Git command failed or timed out during that attempt, the log records it as an error with the command's name, which tells us which step stops. If it shows nothing, I will tell you what we check next.

One more question. Which status does the commit page show for that file, Added, Modified, Deleted or Merge conflict?

Please reply here once the upload is done.

Best regards,

Michel

In this case the status is modified, since I made a change in an existing file.

Upload is done.

Hello Shawn,

Thank you for the upload and the file's status.

The system log of November 2 has no git command that failed or timed out, though it does not record the click itself.

With External Git Client and an SSH key, the Commit button first looks up that key, and in version 2026.3 it does so in a way that can block the page before git starts. We reproduced the freeze in our lab on 2026.3.3 with an SSH remote, where nothing was staged or logged after the click. With a non-SSH remote, the same commit went through. The lookup came with 2026.3.0 and is still in 2026.3.4, so I do not expect an upgrade to change it for now.

Our development team has confirmed this problem and already has a fix for an upcoming update. I will let you know when it is released.

Until then, you can commit from the server instead. Your log shows a sync that pulls and pushes, which the Git page should show as Two-Way. With that setting, PowerShell Universal should close the pending edit and try to push your commit at its next sync, with no Git credentials needed outside it. It did both in that lab with the page frozen. If the page shows another sync behavior, tell me before running anything.

1. On the server where you made the change, open PowerShell as a user who can write to %ProgramData%\UniversalAutomation\Repository (or your repository path if you changed it), and go to that folder. This page runs git in that same folder.

https://docs.devolutions.net/powershell-universal/config/git/

2. Run these two commands, with your own name, email address and message.

git -c safe.directory=* add -A

git -c safe.directory=* -c user.name="Your Name" -c user.email="you@example.com" commit -m "Your message"

3. After the next sync, check that your commit appears in the history of your remote repository.

If it does not, tell me and I will look again.

Best regards,

Michel

Yes, this is how we are working around the issue currently. Git sync picks it up afterwards.