Issue Git repository pull bug (wrong branch pulled)

[Monsieur Bab]

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,

 

[Sebahat.hadzhi]

Hey, @Monsieur Bab . I have run a few tests and there's indeed some inconsistency with the "Latest commits" data shown in the extension - it seems like it's always being "refreshed" with the main branch history. I will consult with our team on that behavior.

However, according to my tests, when I pull from a non-main branch and then manually deploy - the changes are being successfully applied locally. Could you please confirm if on your end the issue is also with commit history branch mismatch under "Latest commits" only or does deploying the changes also fail?

 

[Monsieur Bab]

Hello,

Thank you for your reply and for the time you spent testing this.

We would prefer not to attempt a deployment just to see if it is merely a display issue; this is our production server, and the "main" branch hasn't been updated since 2024. Deploying it could break the website and force us to manually upload "v4" branch files to the FTP to ensure service continuity.
We would prefer to wait until your dev team has had a chance to look into this bug.

Best regards,

 

[Sebahat.hadzhi]

@Monsieur Bab , our team confirmed this is only a "cosmetic" bug specific to AlmaLinux 9.8. Deploy now action will proceed with the selected Branch despite the Latest Commits history being shown that correspond to main. The bug ID is EXTPLESK-14222. At this point, I cannot provide an ETA for the fix. Until the bug be fixed, consider the latest commits history list shown before hitting Pull now and ignore the list shown afterwards. Thank you for bringing our attention to the issue.