GIT with Powershell Universal help
Hello,
We are running GIT for our production PSU which is 2026.1.1. It is currently configured for PUSH Only. We were curious if anyone has setup a test server and changed the Production to PULL while the "test" server was pushing Production changes? We have never done this before so any guidance from the community would be helpful for us.
Recommended Answer
Hello,
Based on the Git sync behavior, the safer pattern would be to avoid having the test server push directly to the same production branch that the production server is pulling from, unless that branch is intentionally your approved production source.
For this type of setup, I would recommend using separate branches. For example, the test or staging PSU instance can work against a dev branch and push changes there. Once those changes are validated, you can merge or create a pull request into the main or production branch. Then the production PSU instance can be configured for One-Way sync against that production branch, so it only pulls approved changes and does not commit or push changes back.
One important point is that the test and production PSU instances should be treated as separate environments. They should not share the same database, scheduler, identities, app tokens, or job history. Git will synchronize the configuration files, but it will not synchronize everything from the PSU environment.
Before changing the production instance from Push-Only to One-Way, I would strongly recommend testing the same workflow against a non-production branch or repository first, and also taking a backup of the PSU repository folder and Git configuration.
The documentation below has more detail about One-Way, Push-Only, and branching strategies:
https://docs.powershelluniversal.com/config/git
Best regards,
Ruben Tapia
All Comments (1)
Hello,
Based on the Git sync behavior, the safer pattern would be to avoid having the test server push directly to the same production branch that the production server is pulling from, unless that branch is intentionally your approved production source.
For this type of setup, I would recommend using separate branches. For example, the test or staging PSU instance can work against a dev branch and push changes there. Once those changes are validated, you can merge or create a pull request into the main or production branch. Then the production PSU instance can be configured for One-Way sync against that production branch, so it only pulls approved changes and does not commit or push changes back.
One important point is that the test and production PSU instances should be treated as separate environments. They should not share the same database, scheduler, identities, app tokens, or job history. Git will synchronize the configuration files, but it will not synchronize everything from the PSU environment.
Before changing the production instance from Push-Only to One-Way, I would strongly recommend testing the same workflow against a non-production branch or repository first, and also taking a backup of the PSU repository folder and Git configuration.
The documentation below has more detail about One-Way, Push-Only, and branching strategies:
https://docs.powershelluniversal.com/config/git
Best regards,
Ruben Tapia