Is there a way I can explicitly add “edges” to the dependency graph to set dependencies that can later be inferred by features such as

--changed-since

? I know of the visibility rules, but they’re essentially a whitelist/blacklist. I’m looking for a way to manage cases of “this is a file that affects how certain other targets run, so their dependents should be calculate-able” e.g. a

setup.cfg

containing tool options. I can set

dependencies

on a file target, but I would like to do the opposite i.e. set dependents of a file. I’m now noticing

__defaults___

are additive rather than being overridden by BUILD files from subtrees, is that always the case?

__defaults__(all=dict(dependencies=["//:setup_cfg"]))