-
Notifications
You must be signed in to change notification settings - Fork 419
Issues: bazelbuild/buildtools
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
import
cc_proto_library
from @protobuf
or @com_google_protobuf
#1307
opened Nov 18, 2024 by
fardream
buildozer fails to find targets that are macros with a return value assigned to a variable
#1306
opened Nov 14, 2024 by
mattnworb
[Bazel CI] Bazel build fails with "no native symbol 'ProtoLangToolchainInfo'"
#1305
opened Nov 13, 2024 by
sgowroji
print
commands are not printed when using buildozer -f
#1301
opened Oct 15, 2024 by
tinder-tannerbennett
[buildifier][Feature Request]: Add Warning for Recursive Glob for Source Files
#1292
opened Sep 9, 2024 by
PieterBunnenberg
WORKSPACE load statements are reordered when reading from stdin
#1268
opened Apr 24, 2024 by
mkosiba
Buildozer: Handle multiple glob arguments in 'set' arguments
#1249
opened Mar 11, 2024 by
stagnation
Buildtools release artifacts are unsigned and have no checksum files
#1239
opened Feb 8, 2024 by
wade-arista
Unable to go install tagged version since introduction of
v
prefix
#1237
opened Jan 29, 2024 by
ileitch
[buildozer]: Support adding symbols instead of literal strings
#1232
opened Jan 18, 2024 by
justhecuke
Previous Next
ProTip!
Follow long discussions with comments:>50.