-
Notifications
You must be signed in to change notification settings - Fork 374
Issues: bazelbuild/bazel-gazelle
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
Author
Label
Projects
Milestones
Assignee
Sort
Issues list
Deps for
go_proto_library
not generated when proto file name matches package name
#1926
opened Sep 17, 2024 by
davidbyttow
Proposal: Add optional gazelle
ConventionChecker
interface to avoid indexing.
#1907
opened Sep 3, 2024 by
tyler-french
go_deps should expose resolved versions for all Go modules it Bazelizes, for external bookkeeping
#1905
opened Aug 29, 2024 by
Buzz-Lightyear
Usage
go_repository
results in surprising behavior due to go mod download
usage
#1904
opened Aug 28, 2024 by
mauriciogg
feat(go_repository): add visibility restrictions to go_repository rules
#1899
opened Aug 28, 2024 by
tyler-french
bug(go_repository): new gazelle can't properly load external repos with old rules_go
#1898
opened Aug 28, 2024 by
tyler-french
gazelle:proto disable
does not propagate into external dependencies with bzlmod
#1854
opened Aug 5, 2024 by
fishy
Feature Request: Record Service and Message names in Proto's fileInfo
#1843
opened Jul 19, 2024 by
ckilian867
Using the repo name rules_go removes proto embed from all go_library rules
#1823
opened Jun 6, 2024 by
jschaf
Gazelle crashes in repository with MODULE but no WORKSPACE
#1815
opened May 29, 2024 by
AttilaTheFun
Previous Next
ProTip!
Type g p on any issue or pull request to go back to the pull request listing page.