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.

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

Rename master to main #423

Closed
Tracked by #1276
Soroosh129 opened this issue Jul 23, 2021 · 7 comments
Closed
Tracked by #1276

Rename master to main #423

Soroosh129 opened this issue Jul 23, 2021 · 7 comments
Milestone

Comments

@Soroosh129
Copy link
Contributor

Verbatim from GitHub documentation:

Many communities, both on GitHub and in the wider Git community, are considering renaming the default branch name of their repository from master. GitHub is gradually renaming the default branch of our own repositories from master to main. We're committed to making the renaming process as seamless as possible for project maintainers and all of their contributors. This repository is our up-to-date guidance on how and when to rename your default branch.

This change could potentially break existing setups but it is increasingly becoming the default in Git repositories.

@lhstrh
Copy link
Member

lhstrh commented Jul 24, 2021

Yes, I agree we should do this at some point. Let's do it some time in the second half of August?

@cmnrd
Copy link
Collaborator

cmnrd commented Jul 26, 2021

I think I am missing something here. Why the change?

@lhstrh
Copy link
Member

lhstrh commented Jul 26, 2021

It's part of an effort to move away from terms like master/slave, black list/white list, etc. Here's an NYT article: https://www.nytimes.com/2021/04/13/technology/racist-computer-engineering-terms-ietf.html

@cmnrd
Copy link
Collaborator

cmnrd commented Jul 26, 2021

Ok, makes sense. I think this could be done together with moving the repository to the lf-lang organization. Then we only need to change our setup once.

@cmnrd
Copy link
Collaborator

cmnrd commented May 31, 2023

We had too many breaking changes, we might as well tackle this one! Perhaps a good strategy is to establish a 'main' branch and let it mirror master for a while. Then we can switch all CI workflows (in other repos) from master to main and eventually make master read only and set 'main' as the main branch. Do we have someone who could be interested in working on this? @petervdonovan perhaps?

@petervdonovan
Copy link
Collaborator

I'm not sure how easy it will be to have another branch mirror master. Why not just do this all at once? Start a new branch called main that is based on master, update all the satellite repositories to track main, delete master, and then deal with anything else that breaks thereafter?

@petervdonovan petervdonovan self-assigned this May 31, 2023
@lhstrh
Copy link
Member

lhstrh commented May 31, 2023

We don't have to delete master, we just have to make it not the default branch and make it read-only. That said, deleting it does make it apparent in which places stale references to master are lingering. I'm fine with the approach @petervdonovan outlines..

@petervdonovan petervdonovan removed their assignment Jun 1, 2023
@lhstrh lhstrh modified the milestones: 0.5.0, 0.6.0 Jul 25, 2023
@lhstrh lhstrh modified the milestones: 0.6.0, 0.7.0 Nov 6, 2023
@lhstrh lhstrh modified the milestones: 0.7.0, 1.0.0 Feb 17, 2024
@lhstrh lhstrh closed this as not planned Won't fix, can't repro, duplicate, stale May 17, 2024
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

No branches or pull requests

4 participants