Facebook
TwitterMonsieur Bab
New Pleskian
- Server operating system version
- AlmaLinux 9.8 (Olive Jaguar)
- Plesk version and microupdate number
- Plesk Obsidian Web Admin Edition 18.0.79 Update #5
Hello,
We have a website on Plesk that have a GitHub repo connected to deploy changes. It is in Deploy Mode manual and is targeting a branch named "v4".
It worked well for 3 years, but we got a bug for 2 weeks now. When we pull changes, the history is from the "main" branch instead of the "v4" branch. We tried to switch to another branch, then get back to "v4" branch: it refresh the card and now display the correct latest commits, but as soon as we click on the Pull button, it get backs to "main" branch latest commits. When pulling, every check are green so we don't think it's a permissions problem. We tried to change the GitHub key but it doesn't resolve the bug.
What to do? Is it a new bug from latest updates of Plesk? We have automatic updates.
Best regards,
We have a website on Plesk that have a GitHub repo connected to deploy changes. It is in Deploy Mode manual and is targeting a branch named "v4".
It worked well for 3 years, but we got a bug for 2 weeks now. When we pull changes, the history is from the "main" branch instead of the "v4" branch. We tried to switch to another branch, then get back to "v4" branch: it refresh the card and now display the correct latest commits, but as soon as we click on the Pull button, it get backs to "main" branch latest commits. When pulling, every check are green so we don't think it's a permissions problem. We tried to change the GitHub key but it doesn't resolve the bug.
What to do? Is it a new bug from latest updates of Plesk? We have automatic updates.
Best regards,
