Skip to content

Conversation

@browniebroke
Copy link
Collaborator

Description

To follow the current conventions, as both git and GitHub now default to main. I think this repo is perhaps the last one where I'm a maintainer and where this is not the case. GitHub has refined the rename workflow a few years back and it's prety painless now, even giving nudges to forks to do the switch.

Before merging this, a maintainer will have to go the General settings page and use the "Reanme branch" button (the one with a pencil)

image

@browniebroke
Copy link
Collaborator Author

I've replicated our branch protection rule currently on master for main

Copy link
Collaborator

@peterthomassen peterthomassen left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

lgtm, thanks.

@browniebroke
Copy link
Collaborator Author

Thanks both! I'm planning to action this tomorrow around midday

@browniebroke browniebroke merged commit 0d0be84 into encode:main Aug 15, 2025
7 checks passed
@browniebroke browniebroke deleted the rename-master-to-main branch August 15, 2025 11:29
@browniebroke
Copy link
Collaborator Author

That all done. Folks with a fork will be prompted by GitHub to rename their branch too

@browniebroke browniebroke added this to the 3.17 milestone Sep 14, 2025
@browniebroke browniebroke changed the title Rename 'master' branch to 'main' Rename master branch to main Oct 29, 2025
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.

3 participants