-
Notifications
You must be signed in to change notification settings - Fork 19
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
gaby: process vscode-go github issue tracker and discussion #51
Comments
gopherbot
pushed a commit
that referenced
this issue
Nov 14, 2024
Allow formats like golang/go#12345 github.com/golang/go/issues/12345 go.dev/issues/12345 in addition to issue number 12345 (default to golang/go) For #51 Change-Id: Id9e26edd2cd876a708dca4ec3cdecb500bcccf07 Reviewed-on: https://go-review.googlesource.com/c/oscar/+/628015 Reviewed-by: Jonathan Amsterdam <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Zvonimir Pavlinovic <[email protected]>
gopherbot
pushed a commit
that referenced
this issue
Nov 15, 2024
Go project has repositories that run separate issue trackers. (e.g. vscode-go, vulndb, ...) Gaby should be able to support cross-repo search and correlation. For #51 Change-Id: I103812460414b9f1628442608c55337c93a18703 Reviewed-on: https://go-review.googlesource.com/c/oscar/+/628016 LUCI-TryBot-Result: Go LUCI <[email protected]> Reviewed-by: Zvonimir Pavlinovic <[email protected]>
Change https://go.dev/cl/628016 mentions this issue: |
Change https://go.dev/cl/628015 mentions this issue: |
Change https://go.dev/cl/629355 mentions this issue: |
gopherbot
pushed a commit
that referenced
this issue
Nov 18, 2024
I don't know why but currently gabby does not call github.Add. And make github.Add no-op if the project is already present in DB (like CL 627778) For #51 Change-Id: I9d3760bad50186a2f03e20f46d76ef164ac675f3 Reviewed-on: https://go-review.googlesource.com/c/oscar/+/629355 Reviewed-by: Zvonimir Pavlinovic <[email protected]> LUCI-TryBot-Result: Go LUCI <[email protected]>
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Unlike most of other Go projects, vscode-go maintains its own GitHub issue tracker and discussion board.
Currently Gaby assumes a single github project (golang/go).
Two paths to explore:
Extend Gaby to handle an org-level project that can consist of multiple repositories and sources.
(Related: implement generalized content model #43)
Deploy a separate Gaby instance - not ideal since vscode-go issues are closely related to gopls that's tracked in the golang/go issue tracker. Some issues are transferred between two issue trackers.
The text was updated successfully, but these errors were encountered: