-
Notifications
You must be signed in to change notification settings - Fork 17.7k
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
x/tools/gopls: Implement action should ignore importing the current package #61830
Comments
Thanks for the report. This is clearly a bug; prioritizing for the next release. |
Change https://go.dev/cl/518915 mentions this issue: |
Sorry, I'm not used to noticing pull requests, and didn't see that you'd already mailed the fix (and so created one myself 🤦). Let's merge yours first, if you can address the commit message. I'll then merge my test. |
Change https://go.dev/cl/519075 mentions this issue: |
@findleyr Sorry, I didn't bother to read through the contribution guidelines (so I didn't know to send an email) . I've resubmitted the changes as per the documentation. (This is my first time submitting code 🙈) |
Hi @tttoad, you need to edit the title and description of your commit message to affect the CL description in Gerrit. Please see more information here: Once that is done, I will merge your change. |
Change https://go.dev/cl/516758 mentions this issue: |
@findleyr done. PTAL. |
For golang/go#61830 Change-Id: Ic30cc528ecfff299a1fc90a17b4e7ccbf5249a8a Reviewed-on: https://go-review.googlesource.com/c/tools/+/518915 Auto-Submit: Robert Findley <[email protected]> TryBot-Result: Gopher Robot <[email protected]> Run-TryBot: Robert Findley <[email protected]> gopls-CI: kokoro <[email protected]> Reviewed-by: Peter Weinberger <[email protected]>
What version of Go are you using (
go version
)?Does this issue reproduce with the latest release?
yes
What operating system and processor architecture are you using (
go env
)?go env
OutputWhat did you do?
exec Implement action.
What did you expect to see?
2023-08-08.10.50.30.mov
What did you see instead?
2023-08-08.11.02.44.mov
The text was updated successfully, but these errors were encountered: