問題文
The editor extension scans for the same categories as the pipeline. What is the point of running the same checks in the editor?
選択肢
- The developer sees a violation before committing, which avoids a pull request that fails for a reason that was knowable locally.
- The extension is the only place custom policies can be authored, so a team without the editor plugin installed is limited to the shipped policy set.
- The extension uploads its results so that issues are created for local findings, which puts unfinished work from a developer machine into the same backlog.
- The editor scan replaces the pipeline scan for the files it covered, so a repository whose developers all use the extension can safely disable the periodic and pull request scans without losing any coverage at all.