-
Notifications
You must be signed in to change notification settings - Fork 677
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
Changing default branch names to main
#2222
Comments
/wg naming |
/sig testing |
@justaugustus – Do you think this merits a communication to k/dev? |
/assign |
@nikhita's initial note to k-dev should suffice at this stage: https://groups.google.com/g/kubernetes-dev/c/jvRPIscaDek/m/1KWEUYXDBQAJ. |
The only impact I can think of for new repos would be that the git.k8s.io redirector ( |
Just to ensure we are on the same page - when we create a new repo in a Kubernetes org after Oct 1, we will set the default branch to |
xref kubernetes/website#21749 - k/website issue about changing their default branch to |
I think this has been handled by their default redirect: https://github.blog/changelog/2020-07-17-links-to-deleted-branches-now-redirect-to-the-default-branch/ It does mean things would be redirected twice, but that's probably the best scenario for the interim till everything has been switched over. |
I'm not sure... that seems to only apply to deleted branches. A new repo that only had a |
I think we should flip the default branch for all repos at once. We'll also need to update our automation (prow, etc). For git.k8s.io specifically, we'll need to update: |
You're right. GitHub has confirmed it as well 👍 As just about all our repos are generated off the kubernetes-template-project, they will have a default branch name of
Before flipping I do think we should test. It will mean the redirector won't work for the ones we do decide to test, but I think thats an acceptable trade-off for now. |
Issues go stale after 90d of inactivity. If this issue is safe to close now please do so with Send feedback to sig-testing, kubernetes/test-infra and/or fejta. |
/remove-lifecycle stale
…On Tue, Dec 29, 2020 at 8:39 PM fejta-bot ***@***.***> wrote:
Issues go stale after 90d of inactivity.
Mark the issue as fresh with /remove-lifecycle stale.
Stale issues rot after an additional 30d of inactivity and eventually
close.
If this issue is safe to close now please do so with /close.
Send feedback to sig-testing, kubernetes/test-infra and/or fejta
<https://github.com/fejta>.
/lifecycle stale
—
You are receiving this because you were mentioned.
Reply to this email directly, view it on GitHub
<#2222 (comment)>,
or unsubscribe
<https://github.com/notifications/unsubscribe-auth/AD24BUHFIWCHZIRQAX6ITVLSXHWJ3ANCNFSM4RYQRYHQ>
.
|
/priority important-longterm |
Pulling down from the description edit I just made: 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. |
ingress-nginx is already using main and dev-v1 as the branches. |
Placeholder enhancement tracking issue for |
/milestone v1.23 |
FYI: we finally wrapped kubernetes/k8s.io#1597 for kubernetes/k8s.io. There were lots of links to the old branch name littered throughout project repos |
quick update from the cluster-api land
|
hey @fabriziopandini , here is the issue where we tracked the change for kubemark, we did not have a pull request though. |
This should probably have a different milestone, if any. This issue seems out of sync / out of date with work tracked elsewhere. |
Quick update here: Kubernetes/kube-state-metrics is done as per kubernetes/kube-state-metrics#1554 |
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
master
tomain
. 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.
The text was updated successfully, but these errors were encountered: