fix(worker): baseline job을 full-history scan으로 처리#52
Conversation
baseline enqueue의 sentinel commit을 단일 commit log opts로 넘기지 않도록 scan-worker 옵션을 분리한다. baseline job은 finding context에 sentinel commit/HEAD branch를 덮어쓰지 않고, scanner가 제공한 history context를 보존한다. 검증: uv run pytest tests/test_scan_worker.py -q && uv run pytest -q && uv run python -m governance.autopilot_gate --base origin/main Co-Authored-By: Codex GPT-5 <noreply@openai.com>
There was a problem hiding this comment.
Code Review
This pull request refactors the scan worker to handle baseline scan jobs differently from incremental ones by introducing helper functions to configure scan options and finding contexts. The review feedback highlights a potential backward-compatibility issue where legacy baseline jobs in the queue might decode with an incremental job type but retain a "baseline" commit SHA, which would cause runtime failures. It suggests checking both the job type and the commit SHA to identify baseline jobs, and adding a corresponding test case to verify this behavior.
Important
The consumer version of Gemini Code Assist on GitHub is being sunset. Starting June 18, 2026, new organization installations will be blocked, and all code review activity will officially cease on July 17, 2026.
For more details on the timeline and next steps, please review the Help Documentation.
What
scan-worker옵션을 분기했습니다.Why
commit_sha=baselinesentinel을 쓰는 queue job이라, 기존 단일 commit log opts(baseline^!)로 실행하면 runtime baseline이 실패합니다.Validation
uv run pytest tests/test_scan_worker.py -quv run pytest -quv run python -m governance.autopilot_gate --base origin/main