This repository was archived by the owner on Jun 11, 2026. It is now read-only.
Repository navigation
This repository was archived by the owner on Jun 11, 2026. It is now read-only.
Proposal: Migrate reactxp's trunk branch from master to main #1221
Description
We've adopted this in my company for most active repos (some holdouts remain but are currently planned to move eventually), and I personally have adopted this in several open source projects.
There was effort involved in changing the CI tooling, but using main allows engineer's auto-complete muscle memory to keep working, so we found no significant issues.
Some context:
Activity
mikehardy commentedon Jul 22, 2020
Just since I have your ear here, can you list out the exact steps that implement this? I'd changed some other projects to allow/deny but haven't changed git branch terms, and I have other repos I'm interested in regardless of how the proposal goes here
For this specific proposal, I doubt it's a voting thing but I like the change. Technically a non-event but positive on a personal level.
erictraut commentedon Jul 22, 2020
Github has announced that they're working on processes and tools to help automate this conversion. I think we should wait a little bit longer for the tools and guidance to be published. I agree with the sentiment though, and I fully support this.
fbartho commentedon Jul 22, 2020
Mike Hardy (@mikehardy) -- the steps I followed was:
master-- ideally all your CI code is checked into the repo, but you may need to edit files somewhere else.git branch -m master mainmainmasterif you have no open PRs that you can't adjustfbartho commentedon Jul 22, 2020
Super timely announcement right after I posted this proposal: https://github.blog/changelog/2020-07-22-github-actions-better-support-for-alternative-default-branch-names/
fbartho commentedon Jul 22, 2020
https://github.com/github/renaming/