[Improvement] Rename default master branch to main

[arturcic]

GitHub already added the feature to rename the default branch and re-target the PRs on the new default branch.

@GitTools/developers do you agree with that?

It will require also adapting the build scripts and maybe the code itself

[asbjornu]

Yes, 👍🏼 from me.

[gep13]

Seems like a good idea to me!

[dazinator]

Whats the benefit?

[asbjornu]

There's a lot of good information here, @dazinator.

[dazinator]

Oh dear. Politics.
I guess everyone who works in master data management is hoping they will go under the radar of this particular political agenda!

[GeertvanHorrik]

@arturcic is this a "visual" / GitVersion branch change only or also a behavioral runtime change in how GitVersion works?

The reason I ask is because I see lots of unit tests changing from master => main but I think we should actually duplicate and test both master and main (and leave it it to the users whether they want to go ahead with this "main branch thing").

[arturcic]

@GeertvanHorrik the tests internally use main to make it consistent, but master is still supported. I introduced the constant MainBranch that is used in the tests, and before the switch it had the master value. This is for the internal code only. As for the consumer, default is main, but you can also use the master in GitVersion.yml as there is a compatibility added.

[arturcic]

That means projects that were using the GitVersion before this change will continue to work

[GeertvanHorrik]

Thanks for the explanation, then I don't mind, as long as it's not a breaking change for people sticking with master 👍

[gep13]

This is a nice touch...

Got that when browsing to repository after rename.

[github-actions]

🎉 This issue has been resolved in version 5.6.5 🎉
The release is available on:

• GitHub Release
• Chocolatey Package
• .Net Global Tool

Your GitReleaseManager bot 📦🚀

[david-driscoll]

Just an FYI I found that this causes a failure when using a branch configuration that currently references master. Changing the source-branches fixes the problem however that seems like an accidental breaking change. ❤️

assembly-versioning-scheme: MajorMinorPatch
mode: ContinuousDeployment
continuous-delivery-fallback-tag: ci
next-version: 0.1.0
branches:
  next:
    regex: ^next$
    mode: ContinuousDeployment
    tag: next
    increment: Major
    prevent-increment-of-merged-branch-version: false
    track-merge-target: false
    tracks-release-branches: false
    is-release-branch: false
    source-branches: ['master']
ignore:
  sha: []

[asbjornu]

@david-driscoll, this should have been fixed in #2588.