RFC 80: Rename master branch to main in all repositories

[foolip]

Rendered

[foolip]

@stephenmcgruer and @Hexcles (feel free to unsubscribe) put together WPT and wpt.fyi - inclusive branch naming last year, which has much of the detail needed here.

[foolip]

If someone would like to take over this RFC and drive it to completion, I would be very happy. It's a lot of work to ensure this change won't break anything given all the repos involved, and also things like https://wpt.fyi/results/?label=experimental&label=master&aligned where we'd need some changes in wpt.fyi.

[gsnedders]

FYI, non-archived repos with default branches which aren't main:

https://github.com/web-platform-tests/code-of-conduct-moderations (master) https://github.com/web-platform-tests/data-migration (master) https://github.com/web-platform-tests/editor (master) https://github.com/web-platform-tests/rfcs (master) https://github.com/web-platform-tests/wpt (master) https://github.com/web-platform-tests/wpt-metadata (master) https://github.com/web-platform-tests/wpt-notes (master) https://github.com/web-platform-tests/wpt.live (master)

It does seem like we should be able to move almost all of these over with minimal risk.

I do wonder if we should split this RFC into two, one covering WPT itself and one covering the rest.

[foolip]

The second riskiest I think might be wpt-metadata, since there are multiple pieces of code creating automated pull requests. Creating a pull request requires a target branch, so that'll need updating.

But I agree splitting into multiple RFC. For the not-wpt RFC, I expect the discussion to just be "try it and see what breaks", for wpt we need to be a bit more responsible.

[foolip]

For anyone coming across this, I do not plan to work on this. Feel free to take it over as a new RFC and I will close this one.