gabyhelp feedback #67901
Replies: 24 comments 37 replies
-
Right now, @gabyhelp is editing recently modified/posted comments and issues. Anywhere the plain text "CL nnn" appears, it changes the text to be a link to go.dev/cl/nnn. I've meant to do this for many years now, so that's the first chore. |
Beta Was this translation helpful? Give feedback.
-
@gabyhelp has also started posting to new issues (plus the issues created in the last two days, to get started) with lists of similar issues, if it finds any that are similar enough. If not, it will stay quiet. Here is one success story: #67887 (comment). And here is another: #67897 (comment). This one is only a partial success because @thepudds got there first, but only because the bot gave him a head start. 😄 |
Beta Was this translation helpful? Give feedback.
-
I imagine this is on your list already, but in case not: another thing that would be nice would be for the bot to rewrite google-internal urls to their public counterparts. |
Beta Was this translation helpful? Give feedback.
-
It might be nice to have gabyhelp not generate emails when posting to issues. I see its updates, particularly related issues posts, as not needing a "ping". It's just additional information put there when you otherwise navigate to an issue. |
Beta Was this translation helpful? Give feedback.
-
I wonder if can be smart enough to recognize misformatted text, especially code blocks. We often see issues with no fences around code blocks or using single backticks (I assume this is from jira's formatting). |
Beta Was this translation helpful? Give feedback.
-
Just a note that the similar issues list in #67861 was not helpful other than the reference to #33818. The issue #67861 was about changing |
Beta Was this translation helpful? Give feedback.
-
I would feel alienated were I nudged to interact with an LLM by merely browsing Go development. I hope you will confine your bot to deterministic, comprehensible actions only. |
Beta Was this translation helpful? Give feedback.
-
Would this bot eventually replace the rather basic "Gopher Robot" at https://go-review.googlesource.com/q/owner:[email protected]? It currently seems to rely on a few heuristics to tell PR/CL authors about common mistakes, such as in https://go-review.googlesource.com/c/build/+/591455. It seems rather similar to the bot discussed here. |
Beta Was this translation helpful? Give feedback.
-
In #67934 gabyhelp correctly reported that the issue was similar to #67933. That is because they are both backport requests for the same original issue. Perhaps gabyhelp can skip backport issues. |
Beta Was this translation helpful? Give feedback.
-
The Go project has a redirector for permalinks. It would be helpful if @gabyhelp could replace links to targets of the redirector (and hopefully, any previous targets if the short link has an history) by the short permalink. |
Beta Was this translation helpful? Give feedback.
-
For my newly filed issue #67953, the related issues that @gabyhelp annotated it with (in #67953 (comment)) are not really all that helpful. Yes, they are all problems with coverage, but don't really relate to the very specific problem at hand. |
Beta Was this translation helpful? Give feedback.
-
The related issues for my issue #67961 (filed using gopls bug) are all empty instances of the gopls bug template. They are 90% similar to mine. Maybe I was too concise in my report! Probably we need to look for empty templates anyway for auto-closing and then exclude them. (It's easy to tell, the empty templates are all 99% similar to each other.) |
Beta Was this translation helpful? Give feedback.
-
Another potential thing to explore is trying to help deduplicate the automated crashes in https://github.com/golang/vscode-go/issues. |
Beta Was this translation helpful? Give feedback.
-
As a relative newcomer to filing issues, I found the Gaby bot helpful for re-categorizing the issue I am filing (i.e editing my own title after the Gaby bot makes its post) (#67984) |
Beta Was this translation helpful? Give feedback.
-
In #67995 (comment), Gaby provided a remarkably accurate summary of the timeline of our feelings about file watching in gopls: the initial issue where we discussed the philosophy of client-side file watching, and then the most relevent issues where we struggled to work around client-side issues, culminating in the current https://go.dev/issue/67995 which I filed to explore server-side file watching. I experienced delight :). |
Beta Was this translation helpful? Give feedback.
-
In #61897 (comment), @gabyhelp appears to have incorrectly edited the text |
Beta Was this translation helpful? Give feedback.
-
#68003 (comment) shows an escaping issue. Brackets in the issue title seem to have broken the markdown in the comment. |
Beta Was this translation helpful? Give feedback.
-
#68054 (comment) was added by gabyhelp as similar issues. They are similar in the sense that they are compiler panics but they are otherwise very much unrelated. |
Beta Was this translation helpful? Give feedback.
-
The code running @gabyhelp is posted on my personal GitHub for now. See https://pkg.go.dev/rsc.io/gaby for docs and https://github.com/rsc/gaby for code. In the near future, we will move it somewhere more official and start taking contributions. |
Beta Was this translation helpful? Give feedback.
-
The @gabyhelp comment on #68212 is a nice illustration of why automatic "closed as duplicate" is so difficult. That one is a duplicate of the top related issue, but the problem is that the fix wasn't backported to 1.22 and 1.21. |
Beta Was this translation helpful? Give feedback.
-
#68220 is pretty clearly a dup of #68170, but gabyhelp didn't find it. |
Beta Was this translation helpful? Give feedback.
-
i'm glad we focus on the important things. |
Beta Was this translation helpful? Give feedback.
-
Gaby posted a response with broken markdown in #68250 (comment) |
Beta Was this translation helpful? Give feedback.
-
I am experimenting with running a new bot @gabyhelp (which I am writing) in the Go issue tracker to try to help automate various mundane things that a machine can do reasonably well. Some aspects of the work may involve AI/LLMs; some will not.
Please thumbs up or thumbs down individual comments from the bot depending on whether they are correct/helpful or not. If the bot is getting in the way, we obviously want to know and fix it.
When the bot posts a comment, it will link back to this discussion page, which is a good place to leave non-boolean feedback. Thanks!
This discussion is also a good place to post ideas for things you wish a bot would do for you in the issue tracker.
To snoop around in all the issues where the bot has commented, you can use this search.
Beta Was this translation helpful? Give feedback.
All reactions