Cannot commit changes to git
After upgrading to Powershell Universal 2026.3.0, we couldn't commit any changes to git in the Admin panel. Adding a commit message and clicking the button does nothing, and immediately following the attempt, all UI elements become unresponsive, such as items on the scope pane, so you cannot navigate away without refreshing the whole page.
Upgrading to 2026.3.3 did not resolve the problem. Running on Windows. Problem persists in all browsers (Firefox, Chrome, Edge).
All Comments (1)
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
Michel Audi