chore: rename default branch from master to main#120
Merged
Conversation
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>
Contributor
There was a problem hiding this comment.
Pull request overview
Prepares the repository for renaming the default branch from master to main by updating branch-name references in CI and documentation so workflows and operational instructions align with the new default branch.
Changes:
- Update CI workflow trigger branch filters from
mastertomain. - Update release automation skill documentation to use
mainin git commands and narrative. - Update Docker publishing documentation to reference
mainfor protected-branch environment publishing.
Reviewed changes
Copilot reviewed 3 out of 3 changed files in this pull request and generated 2 comments.
| File | Description |
|---|---|
.github/workflows/ci.yml |
Switches push/pull_request branch filters to main for CI triggering. |
.claude/skills/spfx-release/SKILL.md |
Updates release-branch/tagging instructions to use main instead of master. |
build-and-push.md |
Updates environment protection guidance to refer to main for Docker publishing. |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Comment on lines
4
to
+9
| push: | ||
| branches: | ||
| - master | ||
| - main | ||
| pull_request: | ||
| branches: | ||
| - master | ||
| - main |
Comment on lines
12
to
+14
| 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 |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Prepares the repo to rename the default branch from `master` to `main`.
Changes
`build-and-push.yaml` is tag-triggered and unaffected. `CONTRIBUTING.md` already referenced `main`.
Follow-up (after merge)
Rename the branch on GitHub (`master` → `main`), which auto-retargets open PRs, migrates branch protection, and sets the default branch.
🤖 Generated with Claude Code