⚠️ Change default branch to "main"

[christopherhein]

Instructions here https://www.kubernetes.dev/resources/rename/

Anytime

• If a presubmit or postsubmit prowjob triggers on the master branch (branches field of the prowjob), add the main branch to the list (see prep kubernetes/org jobs for default branch rename kubernetes/test-infra#20665 for an example).
• If the milestone_applier prow config references the master branch, add the main branch to the config (see Prep kubernetes/k8s.io for default branch rename kubernetes/test-infra#20675 for an example).
• If the branch_protection prow config references the master branch, add the main branch to the config.

Just before rename

• periodic prowjobs, or any prowjob that mentions the master
• If a prowjob mentions master in its name, rename the job to not include the branch name
• If a prowjob calls scripts or code in your repo that explicitly reference master

Finalizing

• Set remote head to track main
• Rename the default branch from master to main
• 🐛 fixing branch name for apidiff #66 fix apidiff branch name

Post-rename

• If a prowjob still references the master branch in the branches field, remove the master branch
  • CAPN Presubmit - removing old branch references kubernetes/test-infra#22309
• If the milestone_applier prow config references the master branch, remove it from the config.
• Send out comms

/kind cleanup
/wg naming

[k8s-ci-robot]

@christopherhein: The provided milestone is not valid for this repository. Milestones in this repository: [next, v0.1.0, v0.1.x]

Use /milestone clear to clear the milestone.

In response to this:

Instructions here https://www.kubernetes.dev/resources/rename/

/kind cleanup
/wg naming
/milestone Next

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.

[christopherhein]

/milestone v0.1.x

[christopherhein]

/assign @kubernetes/owners

As per - https://www.kubernetes.dev/resources/rename/#approval

[spiffxp]

So I see you checked a bunch of boxes but what exactly did you do? Do you have links to PRs or descriptions of why you're good to go?

[christopherhein]

@spiffxp we didn't have a lot of work since this is a relatively new repo, we only have one Prow job which was added recently with this issue in mind - https://github.com/kubernetes/test-infra/blob/master/config/jobs/kubernetes-sigs/cluster-api-provider-nested/cluster-api-provider-nested-presubmits.yaml#L10 and in those the scripts that are called act solely on the branch that was pulled. Both branch_protection and milestone_applier haven't been configured yet.

Additionally, We discussed this on today's CAPN Office hours as well - https://www.youtube.com/watch?v=-bbUzYKHFls&t=5s to pre-emptively get folks ready for when the change goes into effect.

[spiffxp]

You'll want to take care of https://github.com/kubernetes-sigs/cluster-api-provider-nested/blob/fefd2138922b0d24a7ebe8c569cef0bc2f42e242/Makefile#L147

But +1 as a github admin to go ahead

[christopherhein]

Good catch, thank you, I'll get that fixed up after the branch change.

[christopherhein]

Branch has been changed in the Githuh UI and not is tracking the main branch. https://github.com/kubernetes-sigs/cluster-api-provider-nested/tree/main

[christopherhein]

/close
Thanks folks for all your help on this! 🎉
https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/Woe731ONmBc

[k8s-ci-robot]

@christopherhein: Closing this issue.

In response to this:

/close
Thanks folks for all your help on this! 🎉
https://groups.google.com/g/kubernetes-sig-cluster-lifecycle/c/Woe731ONmBc

Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository.