-
Notifications
You must be signed in to change notification settings - Fork 845
Changing default branch names to main #2222
Copy link
Copy link
Open
Labels
area/github-managementIssues or PRs related to GitHub Management subprojectIssues or PRs related to GitHub Management subprojectlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.sig/testingCategorizes an issue or PR as relevant to SIG Testing.Categorizes an issue or PR as relevant to SIG Testing.wg/namingCategorizes an issue or PR as relevant to WG Naming.Categorizes an issue or PR as relevant to WG Naming.
Milestone
Description
Metadata
Metadata
Assignees
Labels
area/github-managementIssues or PRs related to GitHub Management subprojectIssues or PRs related to GitHub Management subprojectlifecycle/frozenIndicates that an issue or PR should not be auto-closed due to staleness.Indicates that an issue or PR should not be auto-closed due to staleness.priority/important-longtermImportant over the long term, but may not be staffed and/or may need multiple releases to complete.Important over the long term, but may not be staffed and/or may need multiple releases to complete.sig/contributor-experienceCategorizes an issue or PR as relevant to SIG Contributor Experience.Categorizes an issue or PR as relevant to SIG Contributor Experience.sig/releaseCategorizes an issue or PR as relevant to SIG Release.Categorizes an issue or PR as relevant to SIG Release.sig/testingCategorizes an issue or PR as relevant to SIG Testing.Categorizes an issue or PR as relevant to SIG Testing.wg/namingCategorizes an issue or PR as relevant to WG Naming.Categorizes an issue or PR as relevant to WG Naming.
Type
Fields
No fields configured for issues without a type.
Organization or repository
All
Users affected
Global
Describe the issue
This is a long-term tracking issue for renaming the default branch on repositories from
mastertomain. Consider this community tracking for the discussion in https://github.com/github/renaming.As of today (9/24):
main: https://github.com/github/renaming#on-october-1-2020-newly-created-repositories-will-default-to-maincc: @kubernetes/owners @kubernetes/wg-naming
/area github-admin
/sig contributor-experience
/wg naming
EDIT(@spiffxp 2021-06-30): Here's an attempt at surveying the state of things today. There are currently 17/243 repos (~7%) that have had their branches renamed.
We need to regroup on the easiest way to track and delegate this. Manually updating a GitHub issue description isn't it, but I thought it would help to see the info here.