-
Notifications
You must be signed in to change notification settings - Fork 127
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
Migrations to golang 1.19 #271
base: master
Are you sure you want to change the base?
Conversation
# Conflicts: # cmd/suite_test.go # go.sum # pkg/reconciler/suite_test.go
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
It's confusing to see the PR structured as is: multiple times a commit is just fixing something which was broken in a previous commit.
This makes the reviewers life harder, and renders tools like git bisect
useless if this happens to be merged.
Could you please squash everything into a single commit - or structure the commits in a better way ?
Finally, I wonder if we should jump to 1.19 now. I personally would only do it once 1.18 goes EOL - meaning, I think the project's go.mod should use the oldest supported version of golang.
Pull Request Test Coverage Report for Build 3188704025
💛 - Coveralls |
@kmlebedev any chance you can rebase? We can take another look at moving to 1.19 thanks for the PR |
What this PR does / why we need it:
migrations to golang 1.19