## Summary
- detect whether BUILDBUDDY_API_KEY is present in Bazel CI
- keep existing remote BuildBuddy path when key is available
- add a local fallback path for fork PRs without secrets by clearing
remote cache/executor/BES endpoints
- document each fallback flag inline with links to Bazel docs
## Testing
- ruby -e 'require "yaml";
YAML.load_file(".github/workflows/bazel.yml"); puts "ok"'
- verified Bazel docs/flag references used in workflow comments
|
||
|---|---|---|
| .. | ||
| bazel.yml | ||
| cargo-deny.yml | ||
| ci.bazelrc | ||
| ci.yml | ||
| cla.yml | ||
| close-stale-contributor-prs.yml | ||
| codespell.yml | ||
| Dockerfile.bazel | ||
| issue-deduplicator.yml | ||
| issue-labeler.yml | ||
| rust-ci.yml | ||
| rust-release-prepare.yml | ||
| rust-release.yml | ||
| sdk.yml | ||
| shell-tool-mcp-ci.yml | ||
| shell-tool-mcp.yml | ||