Rename master to main

[ikarldasan]

What this PR does / why we need it:
Needed for kubernetes/k8s.io#1597

Which issue(s) this PR fixes (optional, using fixes #(, fixes #<issue_number>, ...) format, will close the issue(s) when the PR gets merged):
Needed for kubernetes/k8s.io#1597

[k8s-ci-robot]

Welcome @ikarldasan!

It looks like this is your first PR to kubernetes-sigs/nfs-ganesha-server-and-external-provisioner 🎉. Please refer to our pull request process documentation to help your PR have a smooth ride to approval.

You will be prompted by a bot to use commands during the review process. Do not be afraid to follow the prompts! It is okay to experiment. Here is the bot commands documentation.

You can also check if kubernetes-sigs/nfs-ganesha-server-and-external-provisioner has its own contribution guidelines.

You may want to refer to our testing guide if you run into trouble with your tests not passing.

If you are having difficulty getting your pull request seen, please follow the recommended escalation practices. Also, for tips and tricks in the contribution process you may want to read the Kubernetes contributor cheat sheet. We want to make sure your contribution gets all the attention it needs!

Thank you, and welcome to Kubernetes. 😃

[spiffxp]

/ok-to-test
/lgtm

[k8s-ci-robot]

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: ikarldasan, spiffxp
To complete the pull request process, please assign saad-ali after the PR has been reviewed.
You can assign the PR to them by writing /assign @saad-ali in a comment when ready.

The full list of commands accepted by this bot can be found here.

Needs approval from an approver in each of these files:

• release-tools/OWNERS

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

[pohly]

/hold

"release-tools" should not be modified locally. The same change already went into csi-release-tools and will be copied from there.

[spiffxp]

@pohly is there anything we can do to help the copy take place? I notice this and a number of other repos are still pending (ref: kubernetes/k8s.io#1597 (comment))

[pohly]

@pohly is there anything we can do to help the copy take place?

The change was merged into csi-release-tools and component owners are welcome to refresh their copy of the repo - anyone can do that. I just tend to do it myself for kubernetes-csi with a script because it is less work overall.

I notice this and a number of other repos are still pending (ref: kubernetes/k8s.io#1597 (comment))

I already submitted PRs for csi-test and csi-driver-host-path almost a month ago. We just had problems with inactive default reviewers again 😢 I ran my script again now which created new PRs. Perhaps those get more attention.

I didn't update some of the other repos (including this one here) because I didn't know that they were using csi-release-tools and/or whether automatically generated PRs are welcome. I updated my script to also update repos under the kubernetes-sigs org, but ran into issues with "make test" in nfs-subdir-external-provisioner and nfs-ganesha-server-and-external-provisioner. It might just be a Go version mismatch, but I'd prefer if owners of those repos update csi-release-tools themselves because I don't have the bandwidth to deal with repo specific issues.

[consideRatio]

"release-tools" should not be modified locally. The same change already went into csi-release-tools and will be copied from there.

I suggest we close this in favor of kubernetes-csi/csi-release-tools#165 that updates this as part of release-tools directly.

[pohly]

"release-tools" should not be modified locally. The same change already went into csi-release-tools and will be copied from there.

I suggest we close this in favor of kubernetes-csi/csi-release-tools#165 that updates this as part of release-tools directly.

That nicely avoids the issue of deciding which branch is the latest.

However, someone still needs to take care of updating nfs-ganesha-server-and-external-provisioner.

[consideRatio]

However, someone still needs to take care of updating nfs-ganesha-server-and-external-provisioner.

@pohly yepp! I opened #58 to address what remains here that can be addressed now and not also require an actual rename of branches. I hope that by doing so, #58 can get merged quickly and then the actual migration work related to CI systems etc referencing specific branches can be done with less trouble.

[consideRatio]

kubernetes-csi/csi-release-tools#165 has been merged!

[consideRatio]

This PR correctly fixes a link, but does it in files that are managed centrally in csi-release-tools, which has got its links fixed at this point via kubernetes-csi/csi-release-tools#165.

Other similar changes for this repo has been made in #58.

Should we close this PR at this point?

[spiffxp]

This repo is still showing up in cs.k8s.io as referencing the old links. What needs to happen to pull in the update of csi-release-tools? Then I think we can close this out

[kvaps]

There is another PR which is updating release-tools by the correct way #70

However there are some problems with merging it due to broken OWNER dependencies.

We're waiting for @wongma7 to set correct symlink for OWNERS file before we'll be able to merge it.

[kvaps]

Closed in favor #70 (review)
/close

[k8s-ci-robot]

@ikarldasan: PR needs rebase.

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.

[k8s-ci-robot]

@kvaps: Closed this PR.

In response to this:

Closed in favor #70 (review)
/close

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.