chore: rename default branch from master to main (#120)

Update CI trigger, release skill, and publish docs to reference the
main branch ahead of renaming the default branch on GitHub.

Co-authored-by: Claude Opus 4.8 (1M context) <noreply@anthropic.com>

Author: DonKirkham

.claude/skills/spfx-release/SKILL.md

@@ -20,9 +20,9 @@ Before making changes, verify:
 
 ## Steps to perform
 
-1. **Create a release branch** from the latest master:
+1. **Create a release branch** from the latest main:
    ```
-   git checkout master && git pull
+   git checkout main && git pull
    git checkout -b release/v$ARGUMENTS
    ```
    Branch name must be valid git (no spaces, no colons).
@@ -35,7 +35,7 @@ Before making changes, verify:
 
 3. **Commit changes** with message: `SPFx v$ARGUMENTS - new version updates`
 
-4. **Squash commits on the release branch** (release branch only — never on master, since unrelated commits between the last tag and HEAD would get folded in):
+4. **Squash commits on the release branch** (release branch only — never on main, since unrelated commits between the last tag and HEAD would get folded in):
    - Get the last tag: `git describe --tags --abbrev=0`
    - Soft reset to that tag: `git reset --soft <last-tag>`
    - Re-commit with the same message.
@@ -46,9 +46,9 @@ Before making changes, verify:
    gh pr create --title "feat: new SPFx version v$ARGUMENTS" --body "..."
    ```
 
-6. **After the PR merges**, create and push the tag against the merged commit on master:
+6. **After the PR merges**, create and push the tag against the merged commit on main:
    ```
-   git checkout master && git pull
+   git checkout main && git pull
    git tag v$ARGUMENTS
    git push origin v$ARGUMENTS
    ```

.github/workflows/ci.yml

@@ -3,10 +3,10 @@ name: ci
 on:
   push:
     branches:
-      - master
+      - main
   pull_request:
     branches:
-      - master
+      - main
 
 jobs:
   build:

build-and-push.md

@@ -11,7 +11,7 @@
 ![Docker PAT result](assets/docker-pat.png)
 7. Open Environments in Settings of the Github project: https://github.com/pnp/docker-spfx/settings/environments
 8. Create a new invironment called `DockerHubProd`
-9. Add necessary protection to the environment. For example, you can choose `Protected branches only` so only commits merged to `master` branch will be able to have access for publishing images to Docker Hub
+9. Add necessary protection to the environment. For example, you can choose `Protected branches only` so only commits merged to `main` branch will be able to have access for publishing images to Docker Hub
 10. Create `DOCKER_ORG` environment variable and set value to `m365pnp`.
 11. Create `DOCKER_USERNAME` environment variable and set value that you got in the Docker page above.
 12. Create `DOCKER_PASSWORD` environment secret and set value that you got in the Docker page above.