Migrating remote branch after studio update to new studio version

[MauerwegRunnerBerlin]

Hello,

I've updated the studio to patch 2025-08 after not updating for several months. The existing local branches have been asked to migrate to the new version — I know what has to be done and it works.
When creating a new branch from the main branch, the new branch must first be migrated to the new studio version. This shows that the branch in the Git repository is still in the older version of the studio.

When I try to pull and merge an already migrated local branch, I receive this message.

This also shows that the remote main branch has to be migrated too.

How can I migrate the main branch? This was a colleague's task, but he has left the company.

Could I check it out as a local branch, name it the same and push it?

21 October 2025: I took a look at the old Studio version, and here is the button for switching to remote branches.
This is not the case in Studio 2025-08.

Thanks in advance, Matthias

[Shicong_Hong · Accepted solution]

@MauerwegRunnerBerlin Does the main branch already exist in your local branches? If not, you will need to checkout the main branch as a local branch with the same name (default name). After that, you will be required to migrate the project and then push the changes to the remote server.

Regards

Shicong

[MauerwegRunnerBerlin]

Hello Shicong,

That solved the problem. I didn't know that you could use the same name for checkout as local. I had also opened a support case.
The reason for the problem was the changes in handling GIT in release 2025-07.
Thanks for your help and best regards, Matthias