Facebook
TwitterUsername:
TITLE
Plesk Git pull deploys wrong branch
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian v18.0.72_build20250915.05 os_Windows 2016/2019/2022/2025
PROBLEM DESCRIPTION
After updating Plesk, when performing "Pull now" on a Git repository via the Plesk Git extension, the repository branch is unexpectedly switched to the default repository/branch defined in Git.
In the Plesk GUI the selected repository/branch appears correct, but in the file
vhosts\domain.com\git\test.domain.com\HEAD
the branch reference is overwritten with the default one.
STEPS TO REPRODUCE
ACTUAL RESULT
The file HEAD is modified to point to the default branch (e.g. master).
As a result, even though the GUI shows staging, the content deployed corresponds to master.
EXPECTED RESULT
The HEAD file should remain pointing to the branch selected in the Plesk GUI (e.g. staging) and the deployment should be executed from that branch.
ANY ADDITIONAL INFORMATION
The bug appeared after Plesk update to version Plesk Obsidian 18.0.72 Update 2 and/or Update 3 and not from a Git extension update.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
TITLE
Plesk Git pull deploys wrong branch
PRODUCT, VERSION, OPERATING SYSTEM, ARCHITECTURE
Plesk Obsidian v18.0.72_build20250915.05 os_Windows 2016/2019/2022/2025
PROBLEM DESCRIPTION
After updating Plesk, when performing "Pull now" on a Git repository via the Plesk Git extension, the repository branch is unexpectedly switched to the default repository/branch defined in Git.
In the Plesk GUI the selected repository/branch appears correct, but in the file
vhosts\domain.com\git\test.domain.com\HEAD
the branch reference is overwritten with the default one.
STEPS TO REPRODUCE
- Configure a Git repository in Plesk and set it to use a branch other than the default (e.g. staging).
- Verify in the Plesk GUI that the selected branch is correct.
- Execute "Pull now" from the Plesk Git interface.
- Check the file vhosts\domain.com\git\test.domain.com\HEAD.
ACTUAL RESULT
The file HEAD is modified to point to the default branch (e.g. master).
As a result, even though the GUI shows staging, the content deployed corresponds to master.
EXPECTED RESULT
The HEAD file should remain pointing to the branch selected in the Plesk GUI (e.g. staging) and the deployment should be executed from that branch.
ANY ADDITIONAL INFORMATION
The bug appeared after Plesk update to version Plesk Obsidian 18.0.72 Update 2 and/or Update 3 and not from a Git extension update.
YOUR EXPECTATIONS FROM PLESK SERVICE TEAM
Confirm bug
