rename default branch from `master` to `main` about open-project-1

[ciro-unity]

several smaller PRs

I've never seen this concept happen on this repo yet 🤣

[ciro-unity]

We can do. The only investment is having to keep master for all the existing open PRs, and manually merge them to master first and then to main. But it shouldn't be a big deal of work.
For new PRs - once we make main the default branch, it should just be automatic. Right?

https://github.com/github/renaming

[AlexChesser]

I recently went through this exercise on our production environments at work. Around 50 repos didn't take much time at all. I tend to think the rip-off-the-band-aid approch is needed here, since at no point are there going to be FEWER pull requests.

Pull requests are blissfully easy to edit and it can 100% be done within the github website interface I can't imagine the change taking more than 15 minutes.

1. create a new branch by typing main in the website dropdown and hitting enter

2. in the list of branches choose the change-default-branch button beside master

3. in each of the open PRs select the EDIT button

4. in the subject-line-dropdown alter the BASE to main and save

5. delete master branch

@ciro-unity

[AlexChesser]

For new PRs - once we make main the default branch, it should just be automatic. Right?

yes - all new PRs (will) should come in to main by default once you complete steps 1 and 2 above!

[ManuelRauber]

1. in the subject-line-dropdown alter the BASE to main and save

Ah that's great, I didn't know I could edit the PRs' target branch like that. I'll get on this then.

You can also, if you need to, target another PR for example and GitHub will retarget dependent PRs if the base PR gets merged. Quite nice, if you have a bigger PR for refactoring split into several smaller PRs.

[ciro-unity]

1. in the subject-line-dropdown alter the BASE to main and save

Ah that's great, I didn't know I could edit the PRs' target branch like that. I'll get on this then.