⚠️ Change default branch to "main" about cluster-api-provider-nested HOT 10 CLOSED

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

from cluster-api-provider-nested.

@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.

from cluster-api-provider-nested.

/milestone v0.1.x

from cluster-api-provider-nested.

/assign @kubernetes/owners

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

from cluster-api-provider-nested.

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?

from cluster-api-provider-nested.

@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.

from cluster-api-provider-nested.

You'll want to take care of

But +1 as a github admin to go ahead

from cluster-api-provider-nested.

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

from cluster-api-provider-nested.

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

from cluster-api-provider-nested.

@christopherhein: Closing this issue.

from cluster-api-provider-nested.