envoyproxy / envoyproxy/toolshed
Dont force setup of `@pip3` in bazel workspace
Open
- Dominant language
- Python
- Stars
- 12
- Forks
- 24
- Avg merge
- 6h 37m
- Merged PRs (30d)
- 92
Description
Probably we can use label_flags etc to define where the deps come from and remove the need to set this up
Contributor guide
No contributing guide indexed for this repository
Assessment
This issue has not been assessed yet.