Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Branch rename: master -> main #6739

Closed
jelster opened this issue Jun 30, 2020 · 6 comments
Closed

Branch rename: master -> main #6739

jelster opened this issue Jun 30, 2020 · 6 comments
Assignees
@DHowett
Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Task It's a feature request, but it doesn't really need a major design. Product-Meta The product is the management of the products. Resolution-Fix-Available It's available in an Insiders build or a release

Comments

@jelster
Copy link
Contributor

jelster commented Jun 30, 2020

Description of the new feature/enhancement

I know that there could be a decent amount of effort involved in this for a repos with such a large footprint, but I think there's no time like the present to "commit" ourselves (oh god the pun! the 🔥) to (seriously) Doing Better as people, developers, and as global citizens.

I propose renaming the current master branch to main as an acknowledgement of the community's commitment to recognizing the existence of racial injustice. However small or trivial an act it may seem to some, I feel that it's a worthwhile undertaking.

As a phrase I'm oft known to cite goes, "excellence is a game of inches".

The IETF presents a detailed discussion of the reasons why this it is important to note the terminology of branch names, and should be considered a highly useful resource for basing any discussions around context, pertinence, or applicability.

Proposed technical implementation details (optional)

Just spitballing OTOMH the things that might be considered as part of executing on this. Obviously, whomever does this would need to have appropriate repos perms :)

  1. Coordinate with any dependent repos' owners on logistics/timing(if needed) ❓
  2. Disable CI/CD pipelines and PR bots
  3. Create main branch via operation with master checked out via git branch -m master main (note the -m to keep history intact)
  4. Push to main origin
  5. change default branch in GH from master to main
  6. Configure main branch protection, security, etc rules in GH
    5a. Archive/lock or otherwise deprecate master branch
  7. Re-Enable CI/CD, test/adjust build scripts (if/as needed)
  8. Notify downstream repos ❓
@jelster jelster added the Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. label Jun 30, 2020
@ghost ghost added Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting Needs-Tag-Fix Doesn't match tag requirements labels Jun 30, 2020
@KalleOlaviNiemitalo
Copy link

PowerShell/PowerShell#12951 (comment) suggests that GitHub might do something to make renaming less disruptive. It may be better to wait for that.

@DHowett
Copy link
Member

DHowett commented Jul 2, 2020

I'm in support of this, and will assign myself. If there's the possibility that MSFT will roll out a self-service tool that'll properly update refs, PRs, and internal forks I'd prefer to wait for that.

@DHowett DHowett self-assigned this Jul 2, 2020
@DHowett DHowett added Area-Build Issues pertaining to the build system, CI, infrastructure, meta Product-Meta The product is the management of the products. labels Jul 2, 2020
@ghost ghost removed the Needs-Tag-Fix Doesn't match tag requirements label Jul 2, 2020
@DHowett DHowett added Issue-Task It's a feature request, but it doesn't really need a major design. and removed Issue-Feature Complex enough to require an in depth planning process and actual budgeted, scheduled work. Needs-Triage It's a new issue that the core contributor team needs to triage at the next triage meeting labels Jul 2, 2020
DHowett added a commit that referenced this issue Oct 21, 2020
@DHowett
Prepare for the primary branch name to change to main
0c8b7f0 
This commit fixes up all references to `master` in the source, docs,
specs and comments.
Related to #6739.
@DHowett DHowett mentioned this issue Oct 21, 2020
Merged
@DHowett
Copy link
Member

DHowett commented Oct 21, 2020

We now have a self-service tool that'll do this and retarget all open PRs and stuff, so here goes!

image

(I'll press it once #7985 merges.)

@jelster
Copy link
Contributor Author

jelster commented Oct 21, 2020 via email •
edited by ghost
Loading

@WSLUser

This comment has been minimized.

Sign in to view
@DHowett DHowett added the Resolution-Fix-Available It's available in an Insiders build or a release label Oct 22, 2020
@DHowett
Copy link
Member

DHowett commented Oct 22, 2020

Done!

@DHowett DHowett closed this as completed Oct 22, 2020
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Assignees

@DHowett DHowett

Labels
Area-Build Issues pertaining to the build system, CI, infrastructure, meta Issue-Task It's a feature request, but it doesn't really need a major design. Product-Meta The product is the management of the products. Resolution-Fix-Available It's available in an Insiders build or a release
Projects
None yet
Milestone
No milestone
Development

No branches or pull requests
4 participants
@DHowett @jelster @WSLUser @KalleOlaviNiemitalo