ci(docs): Add agentic workflows for codebase documentation #5649
1 issue
code-review: Found 1 issue (1 high)
High
MCP Gateway step references non-existent step outputs, causing empty credentials - `.github/workflows/docs-codebase-refresh.lock.yml:647-648`
Lines 647-648 reference steps.safe-outputs-start.outputs.api_key and steps.safe-outputs-start.outputs.port, but the safe-outputs-start step (line 624) doesn't produce any outputs. The correct references should be steps.safe-outputs-config.outputs.safe_outputs_api_key and steps.safe-outputs-config.outputs.safe_outputs_port from the earlier step that generates these values. This will cause the MCP Gateway to receive empty API key and port values, likely breaking authentication.
Also found at:
.github/workflows/docs-codebase-update.lock.yml:647-648
Duration: 9m · Tokens: 738.7k in / 11.2k out · Cost: $0.90 (+extraction: $0.00, +merge: $0.00, +fix_gate: $0.00)
Annotations
Check failure on line 648 in .github/workflows/docs-codebase-refresh.lock.yml
sentry-warden / warden: code-review
MCP Gateway step references non-existent step outputs, causing empty credentials
Lines 647-648 reference `steps.safe-outputs-start.outputs.api_key` and `steps.safe-outputs-start.outputs.port`, but the `safe-outputs-start` step (line 624) doesn't produce any outputs. The correct references should be `steps.safe-outputs-config.outputs.safe_outputs_api_key` and `steps.safe-outputs-config.outputs.safe_outputs_port` from the earlier step that generates these values. This will cause the MCP Gateway to receive empty API key and port values, likely breaking authentication.
Check failure on line 648 in .github/workflows/docs-codebase-update.lock.yml
sentry-warden / warden: code-review
[KYA-XLN] MCP Gateway step references non-existent step outputs, causing empty credentials (additional location)
Lines 647-648 reference `steps.safe-outputs-start.outputs.api_key` and `steps.safe-outputs-start.outputs.port`, but the `safe-outputs-start` step (line 624) doesn't produce any outputs. The correct references should be `steps.safe-outputs-config.outputs.safe_outputs_api_key` and `steps.safe-outputs-config.outputs.safe_outputs_port` from the earlier step that generates these values. This will cause the MCP Gateway to receive empty API key and port values, likely breaking authentication.