Add --prune_unused_actions option to aquery to prune unreachable actions When `--prune_unused_actions` is specified on the command line, `aquery` emits only actions that are reachable in the artifact dependency graph of the requested top-level targets' default output artifacts (or requested `--output_groups`). ### Motivation When querying an analyzed target (such as `deps(//foo)`), `aquery` currently emits all actions associated with every analyzed configured target in the query scope. This includes actions that produce unused outputs—such as `.pic.o` static compilation outputs when linking a dynamic library, or auxiliary artifacts in a dependency that are never referenced by the top-level target. This addresses [#14156](https://github.com/bazelbuild/bazel/issues/14156) by allowing users to prune unreachable actions directly in `aquery`, eliminating the need for post-processing the action graph dump. PiperOrigin-RevId: 972474542 Change-Id: Icb77dd7fb58ea29c83da20defa02862a227dd242
{Fast, Correct} - Choose two
Build and test software of any size, quickly and reliably.
Speed up your builds and tests: Bazel rebuilds only what is necessary. With advanced local and distributed caching, optimized dependency analysis and parallel execution, you get fast and incremental builds.
One tool, multiple languages: Build and test Java, C++, Android, iOS, Go, and a wide variety of other language platforms. Bazel runs on Windows, macOS, and Linux.
Scalable: Bazel helps you scale your organization, codebase, and continuous integration solution. It handles codebases of any size, in multiple repositories or a huge monorepo.
Extensible to your needs: Easily add support for new languages and platforms with Bazel's familiar extension language. Share and re-use language rules written by the growing Bazel community.
To report a security issue, please email security@bazel.build with a description of the issue, the steps you took to create the issue, affected versions, and, if known, mitigations for the issue. Our vulnerability management team will respond within 3 working days of your email. If the issue is confirmed as a vulnerability, we will open a Security Advisory. This project follows a 90 day disclosure timeline.
See CONTRIBUTING.md
