Closed gyliu513 closed 6 years ago
@gyliu513 Apologies for letting this sit for so long! This looks reasonable to me overall. Was there a different version of the docs dependencies pulled in by kubebuilder? I noticed a significant amount of churn there which I didn't look at in detail.
@perotinus I will check more for this, but for now, the 0.1.12 has just released, so I'd prefer that we upgrade to 0.1.12 directly in this PR, what do you think?
/retest
@gyliu513 Thank you! Upgrading to 0.1.12 seems like the right approach to me as well.
Can you adjust the comment message on the first commit, https://github.com/kubernetes/cluster-registry/pull/244/commits/ff31d318b867176bbd211e3e07148e522b204f58? Other than that, LGTM.
@perotinus the first pr is updating to 0.11, and the second pr is updating to 0.12 at https://github.com/kubernetes/cluster-registry/pull/244/commits/c3a4a4ae352d8d678f06b22a3c2ecf5961f50024
Can we keep the commit message as it is as this can reflect the work process of this PR?
@gyliu513 Sure, that seems fine to me. In that case, can you update the commit message of https://github.com/kubernetes/cluster-registry/commit/c3a4a4ae352d8d678f06b22a3c2ecf5961f50024 so that it specifies that it's updating to 0.12?
@perotinus the commit message does include 0.1.12 https://github.com/kubernetes/cluster-registry/commit/c3a4a4ae352d8d678f06b22a3c2ecf5961f50024
/lgtm /approve
[APPROVALNOTIFIER] This PR is APPROVED
This pull-request has been approved by: gyliu513, perotinus
The full list of commands accepted by this bot can be found here.
The pull request process is described here
@gyliu513 Ah, OK, sorry about that.
Fixed https://github.com/kubernetes/cluster-registry/issues/243
/cc @font @madhusudancs @perotinus @pmorie
/sig multicluster