As per the default branch name migration docs, the Cluster API Provider Nested (CAPN) folks want to make you all aware we’ve migrated to using the main branch name, if you have previously cloned/worked on CAPN locally you’ll want to review the Github docs for updating your local tracking branches.
Tracking Issue: https://github.com/kubernetes-sigs/cluster-api-provider-nested/issues/47
Huge shoutout to the entire Naming Working Group and Github Management Group for making this a straight forward and easy process! 🎉
Thanks!--
Chris Hein
You received this message because you are subscribed to the Google Groups "Kubernetes WG Naming" group.
To unsubscribe from this group and stop receiving emails from it, send an email to kubernetes-wg-na...@googlegroups.com.
To view this discussion on the web visit https://groups.google.com/d/msgid/kubernetes-wg-naming/c16ae9f7-3b66-42c4-a85c-4612b078d1d7%40Spark.