DO NOT MERGE YET

Pull request checklist

Please check if your PR fulfills the following requirements:

• Tests for the changes have been added (for bug fixes / features)
• Docs have been reviewed and added / updated if needed (for bug fixes / features)
• Build (npm run build) was run locally and any changes were pushed
• Unit tests (npm test) were run locally and passed
• E2E Tests (npm run test.karma.prod) were run locally and passed
• Prettier (npm run prettier) was run locally and passed

Pull request type

Please check the type of change your PR introduces:

• Bugfix
• Feature
• Refactoring (no functional changes, no api changes)
• Build related changes
• Documentation content changes
• Other (please describe):

What is the current behavior?

Today, the primary branch in Stencil Core is named 'master'. Although GitHub has tooling around moving the primary branch (renaming it), it doesn't fix all the hardcoded references in the codebase.

GitHub Issue Number: N/A

What is the new behavior?

update all references to the code of conduct and contributing guidelines
to use 'main' instead of 'master'

update github workflows to use main instead of master

update the release notes tooling

Does this introduce a breaking change?

• Yes
• No

Testing

There are two things I could not test that could break

1. GitHub workflows - since we haven't renamed the branch yet, it's hard to tell if this 'just works'. However, I am confident that if it breaks, we'll know very quickly 😉
2. Release tooling - likewise with workflows. If this breaks, this is pretty easy to work around with the any-branch flag

Other information

• Stencil Site Changes docs(git): point stencil core links back to main branch site#779
• There's one super old pwa repo using a stencil repo link that I didn't bother to update
• Obviously, this only affects stencil core, and doesn't affect other repos, nor rename the branch itself