Rename master branch to main

[delvedor]

As titled.
It should not be a problem here, but the documentation build should be updated.

Related: https://github.com/github/renaming

/cc @lmammino

[mcollina]

Go for it!

[jsumners]

This is just a solution in search of a problem. And implementing it is going to cause problems for everyone who has the code forked.

[delvedor]

@jsumners I don't agree, if you are maintaining a fork for a pr changing the base branch is the same as changing it when targeting the wrong branch or when we switch from next to master.
Once we do this, we'll ping the authors of every open pr (again, like we did when we switched from next to master) to let them know that they need to rebase on a new branch (with zero breaking changes in this case).

[mcollina]

The tooling provided by github is going to do all the rebasing automatically, it would also allow the old references to continue working. We can also wait for Node.js core to switch for example and validate the approach.

[zekth]

Those references need to be changed:
https://github.com/fastify/fastify/blob/master/.github/workflows/website.yml#L6
https://github.com/fastify/fastify/blob/master/.github/workflows/package-manager-ci.yml#L6

[zekth]

Once we do this, we'll ping the authors of every open pr (again, like we did when we switched from next to master) to let them know that they need to rebase on a new branch (with zero breaking changes in this case).

Renaming a branch will:
Re-target any open pull requests

Not even sure it is necessary

[delvedor]

Latest GitHub news about this:

https://github.blog/changelog/2021-01-19-support-for-renaming-an-existing-branch/

[veritem]

May I go for this one

[Eomm]

Yes, of course

I would suggest this roadmap:

• update docs to HEAD (example https://github.com/pkgjs/support/pull/41/files )
• one core maintainer should rename to the main branch*
• check the fastify/website still works
• update the workflows

This worked well

*to update the local references:

git branch -m master main
git fetch origin
git branch -u origin/main main

[mcollina]

The website integration would need to be fixed.

[mcollina]

This was done

[10xLaCroixDrinker]

Any plans to do this for any of the 93 remaining fastify repos that use a master branch?

[mcollina]

@10xLaCroixDrinker possibly, but it really depends on admins time. There are no tools to massively change github settings inside and org.

[10xLaCroixDrinker]

@mcollina would PRs to update references to master within those repos actions, scripts, docs etc, be helpful to work toward that?

[mcollina]

Realistically yes, but it's still a lot of effort to rename the repos and test it all works correctly.

I'd recommend opening a fresh issue.