convert master branch to main for OSS site + enable `develop` branch protection

to comply with our branch naming conventions we should change these branch names and also enforce some simple branch protection on the develop branch

Acceptance Criteria

• change master to main

A nice how to: https://stevenmortimer.com/5-steps-to-change-github-default-branch-from-master-to-main/

Branch rules:

• require pull request before merging > with 1 approver
• Dismiss stale pull requests approvals where new commits are pushed
• include administrators

[rudouglas]

Created new Branch protection rule for develop with following:

• Require pull request reviews before merging
  • Required approving reviews: 1
  • Dismiss stale pull request approvals when new commits are pushed
• Include administrators

Change master to main

Steps needed

• Create main branch locally, taking the history from master
  • git branch -m master main
• Push the new local main branch to the remote repo (GitHub)
  • git push -u origin main
• Connect main branch to Amplify
• Switch site to build from the main branch instead of master in Amplify
• Check Workflows for actions that involve master branch and change those to main
• Delete the master branch on the remote
  • git push origin --delete master

[rudouglas]

As we are opening a fresh ticket to look at the impact of removing master i’ll close this out