Default branch of synchronized repository is wrong when source has master as default branch

[pc-ahrens]

When synchronizing a repository with default branch master to GitHub Enterprise Server, the default branch is wrongly set the first branch in the list of available branches after synchronization.

Repositories with default branch main do have the correct default branch after synchronization.

Ideally, the actions-sync should be able to handle any case. Otherwise we will need to adjust the default branch after synchronization.

[ajaykn]

Thanks @pc-ahrens for reaching out.
This is intended behaviour currently.

When we are syncing the repo for first time that doesn't exists in enterprise instance, we create repo by default with main branch if exists. If not, it picks up the first one from existing branches.

So in this case, we need to set/change the default branch manually as a one time operation.

We have added this to our backlog and will priortize if there are more customers expecting this.

[AdrianDsg]

I'd be very grateful if @ajaykn could share a short update on this. Has there been any news since January 2023?

[hepcat72]

How do you manually set a default branch? Super-linter in my case is selecting master, but we use main, so it craps out saying the default branch doesn't exist.

[github-actions]

This issue is stale because it has been open for 30 days with no activity.