Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

delete go.mod in root directory #2333

Closed
wants to merge 1 commit into from
Closed

delete go.mod in root directory #2333

wants to merge 1 commit into from

Conversation

hwdef
Copy link
Member

@hwdef hwdef commented Oct 23, 2020

Fix #1813 again

@k8s-ci-robot k8s-ci-robot added the cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. label Oct 23, 2020
@k8s-ci-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is NOT APPROVED

This pull-request has been approved by: hwdef
To complete the pull request process, please assign timothysc after the PR has been reviewed.
You can assign the PR to them by writing /assign @timothysc 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:

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

@k8s-ci-robot k8s-ci-robot added sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. labels Oct 23, 2020
@fabriziopandini
Copy link
Member

The go-mod file in the root directory gets automatically generate when updating go modules under kinder/ or operator/, so IMO there is no point in continuing to delete it
I'm +1 for closing this PR

@hwdef
Copy link
Member Author

hwdef commented Oct 23, 2020

Maybe you can find a way to not generate it.
Or give a warning when viewing code, if someone generates this file.

This file is actually useless.

@fabriziopandini
Copy link
Member

Feel free to open an issue and propose other solutions, but please take care such solutions are not adding any burden to people working in this repo.
In the meantime, I don't see any problem in keeping the file

@hwdef
Copy link
Member Author

hwdef commented Oct 23, 2020

fine.

just close this.

@hwdef hwdef closed this Oct 23, 2020
@hwdef
Copy link
Member Author

hwdef commented Oct 23, 2020

@fabriziopandini
What command did you used?
I try to update go modules under kinder/ or operator/, but go.mod in root directory is not recreate.

@hwdef hwdef reopened this Oct 23, 2020
@hwdef
Copy link
Member Author

hwdef commented Oct 24, 2020

/assign @neolit123

Can you give me some suggestions?
Or we can add go.mod to .gitignore.

@fabriziopandini
Copy link
Member

fabriziopandini commented Oct 24, 2020

TBH, it will be really weird for me to have go.mod in .gitignore, even weirder than having the file itself given that it does not cause any harm

As explained before, as a maintainer of this project, I don't want this to get into the way of contributors again given that after the first PR got merged it was regenerated by simply working on kinder/on the operator.

Also, as soon as the details about the move of kubeadm out of K/K will be addressed, this file will be required, so any effort to remove it is just temporary.

I'm -1 to get this merged
🤷‍♂️

@hwdef
Copy link
Member Author

hwdef commented Oct 24, 2020

It is wrong to keep files just because there are no problems, and it will cause more and more garbage.
I looked at the file history, this file was submitted by you, and it is not surprising that you object to cleaning it.
Maybe others do not agree to clean up this file, but I still think that you uploaded this file as a mistake.
You can +1 or -1, but please don’t promote bad habits.

@hwdef
Copy link
Member Author

hwdef commented Oct 24, 2020

@fabriziopandini
And please let me ask again, what command did you use to upgrade? Did you make a mistake that caused this file to be generated?

@hwdef hwdef closed this Oct 25, 2020
@fabriziopandini
Copy link
Member

what command did you use to upgrade? Did you make a mistake that caused this file to be generated?

The file was generated working on the operator, but TBH I don't remember if this happened while updating some reference or by running some hack/verify script.
However this is going to be revised as per #2317, and this will revamp most of the initial experiment + update to the latest version of golang, so might be the problem will be fixed during this effort

@neolit123
Copy link
Member

neolit123 commented Oct 26, 2020 via email

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cncf-cla: yes Indicates the PR's author has signed the CNCF CLA. sig/cluster-lifecycle Categorizes an issue or PR as relevant to SIG Cluster Lifecycle. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

4 participants