Skip to content

Prepare workflows for master -> main rename#14

Merged
marianogoldman merged 1 commit into
masterfrom
chore/rename-master-to-main
Jun 21, 2026
Merged

Prepare workflows for master -> main rename#14
marianogoldman merged 1 commit into
masterfrom
chore/rename-master-to-main

Conversation

@marianogoldman

Copy link
Copy Markdown
Contributor

What

Preparatory step before renaming the default branch mastermain.

  • php.yml: CI now triggers on both master and main so PRs keep running CI (and satisfying the required PHP 8.4/PHP 8.5 checks) throughout the rename. Without this, PRs targeting main would not trigger CI and would be blocked by branch protection.
  • update-changelog.yml: checkout ref and commit branch point at main (release-triggered, so no transition issue).
  • CHANGELOG.md: Unreleased link points at /commits/main.

Next steps (after merge)

  1. Rename mastermain on GitHub (moves branch protection, retargets open PRs, updates the default branch).
  2. Follow-up PR to drop master from the CI branch filters, leaving [ main ].
  3. Contributors re-point their local clones.

🤖 Generated with Claude Code

Make CI trigger on both master and main during the transition so PRs
keep running while the default branch is renamed, and point the
changelog automation and Unreleased link at main.

A follow-up will drop master from the CI filters once the rename is done.

Co-Authored-By: Claude Opus 4.8 (1M context) <[email protected]>
@marianogoldman marianogoldman marked this pull request as ready for review June 21, 2026 11:32
@marianogoldman marianogoldman merged commit 7784fce into master Jun 21, 2026
2 checks passed
@marianogoldman marianogoldman deleted the chore/rename-master-to-main branch June 21, 2026 11:33
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant