janpeter visser
c82a7b1c06
When a task targets a different repo than its parent product (e.g. an MCP-server task tracked under the main product's PBI), product.repo_url points to the wrong place. Result observed in story 'Verify-gate' batch (2 May): agent's gate-task work failed to push because product was Scrum4Me but the code lives in scrum4me-mcp. Add optional `Task.repo_url` (TEXT, nullable). scrum4me-mcp's `resolveRepoRoot` will read this in a follow-up PR — null falls back to product.repo_url, preserving current behaviour for the 99% case. Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
4 lines
241 B
SQL
4 lines
241 B
SQL
-- AlterTable: optional repo_url override on Task. Used when an MCP-server
|
|
-- task is tracked under a different product's PBI (cross-repo support).
|
|
-- Falls back to product.repo_url when NULL.
|
|
ALTER TABLE "tasks" ADD COLUMN "repo_url" TEXT;
|