-
Notifications
You must be signed in to change notification settings - Fork 486
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
Contributing guide (and related) clean up #3538
Conversation
@@ -1,7 +1 @@ | |||
pkg/operator/crds/*.yaml linguist-generated=true | |||
|
|||
# Git on Windows may automatically check out files with crlf line endings, | |||
# which breaks the Fuzz parser in 1.18 (golang/go#52268). A fix is scheduled |
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.
This issue is solved in 1.19 and we use Go 1.19 as per go.mod
.
github.com/grafana/process-exporter v0.7.3-0.20210106202358-831154072e2a h1:JUnP/laSl2GylHT0+fqAqOZY+7XkLh1mLefLN0n8Mmk= | ||
github.com/grafana/process-exporter v0.7.3-0.20210106202358-831154072e2a/go.mod h1:RMjrx3Qn8l2pgCD27g45xbko4UDpVVuHC8Cd2YXPtWA= |
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.
go mod tidy
removed this and I didn't find any imports in the source. I hope it's not here for some magic purpose?
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.
No, we just don't have a CI step (yet) trying to make sure the go.sum
is always tidied, so sometimes this happens.
e9558b1
to
5a6eb34
Compare
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.
LGTM, thanks!
PR Description
Minor clean up performed while following the contributing guide.
Mostly related to the fact that we now use Go 1.19.
Which issue(s) this PR fixes
N/A - trivial fixes and improvements such as this one do not require an issue.