root/fusion
1
0
Fork 0
Code Issues Pull Requests Actions Packages Projects Releases Wiki Activity

feat(FN-3943): align tracking resolution to honor task-level override seman

Browse Source 
Aligned GitHub tracking resolution to resolve task-level overrides, with regression tests covering the create-flow path and documentation of the override semantics.

Fusion-Task-Id: FN-3943
This commit is contained in:
Fusion
2026-05-10 12:05:59 -07:00
committed by gsxdsm
parent c238712a3f
commit 337e287ced
8 changed files with 282 additions and 44 deletions
Download Patch File Download Diff File Expand all files Collapse all files

1
docs/task-management.md
View File

@@ -389,6 +389,7 @@ Tracking behavior is controlled per task:
- `task.githubTracking.repoOverride` optionally forces a specific target repo (`owner/repo`).
- In the dashboard **Task Detail** modal, eligible existing tasks (`triage`, `todo`, `in-progress`, `in-review`) always show GitHub tracking controls so tracking can be enabled, disabled, or retargeted without reopening the task in a creation flow.
- Clearing the Task Detail repo override stores `null`, which reverts repo resolution to project/global defaults.
- Explicit task-level enablement is honored even when project/global GitHub tracking defaults are unset. If `enabled: true` and the repo resolves at task scope (for example via `repoOverride`), Fusion still attempts create-time tracking-issue creation.
Repository resolution order: