It would be useful for it to know about this. Currently the service is aware of two configs per run: the service config, and the project config. This works for project-specific analyzers, on the assumption that an analyzer should either be known to all users (in the service config) or known to just the project (in the project config).
The specific use case I have in mind is with the Fuchsia configs -- with the Fuchsia configs, each repo has its own project config, but I'd love to be able to define a Fuchsia-specific analyzer once in the Fuchsia repo, rather than defining it in every project or in the wider service config.
Comment 1 by mar...@chromium.org
, Sep 18Status: Available (was: Untriaged)