Skip to content

Remove TODO: Now past Bazel 0.29 so can go back to using '...' in CI #424

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.

Sign up for GitHub

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

Merged
merged 2 commits into from
Mar 11, 2021
Merged

Remove TODO: Now past Bazel 0.29 so can go back to using '...' in CI #424

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
e01f4a6
now past Bazel 0.29 so can go back to using '...' in CI for build_tar…
Mar 2, 2021
126ee3a
Merge branch 'master' into jonathon--remove-TODO-in-CI-presubmit-mar2021
Mar 11, 2021
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
12 changes: 1 addition & 11 deletions .bazelci/presubmit.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,20 +1,10 @@
# We exclude docs/ from build_targets. Since we can't blacklist specific target
# patterns (bazelbuild/continuous-integration#779), we have to explicitly
# list every other top-level package in build_targets.
# TODO(#144): When Bazel 0.29 is released, the docgen workflow will work, and
# we can go back to using `...` for build_targets.
---
buildifier:
version: latest
warnings: "all"
all_targets: &all_targets
build_targets:
- "//examples/..."
- "//experimental/..."
- "//packaging/..."
- "//python/..."
- "//tests/..."
- "//tools/..."
- "..."
# As a regression test for #225, check that wheel targets still build when
# their package path is qualified with the repo name.
- "@rules_python//examples/wheel/..."
Expand Down