Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
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
Switch to letting
go get
mutatego.mod
#3590Switch to letting
go get
mutatego.mod
#3590Changes from all commits
9551b73
df0497a
5ef6efb
acce03d
05cb135
8cb409c
a13eeee
7c75b11
433a4f1
8aff846
478dc2c
475b919
73cecb7
b466bb1
4233836
caaf083
File filter
Filter by extension
Conversations
Jump to
There are no files selected for viewing
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.
The test was failing. The backstory is pretty complicated:
go mod tidy
didn't flag it.go 1.16
,go get -d
started flagging the error again.go get -d
togo get -d <dep>@<version>
this error is no longer thrown. Instead thego.mod
file gets updated.I manually replicated the
go get -d github.com/googleapis/[email protected]
followed bygo mod tidy -e
and then updated the test to match what I'm seeing in thego.mod
file.Surprisingly though, the test is still failing complaining that the line isn't present.
So now I'm unclear if the test is wrong somehow, or if there's some wrong code, or what. I'm hesitant to "fix" the test to something that doesn't match the output from when I manually ran the steps.
Anyone else want to take a stab at it?