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

feat(FN-3202): handle manual PR linking and feedback follow-ups

Browse Source 
- Add scheduler logic to create dependency-linked follow-up tasks when actionable PR feedback remains after a PR is merged or closed
- Update engine runtime/project wiring to support manual PR create flows and branch publish behavior for fusion/<task-id>
- Add dashboard route coverage for manual PR creation/linking behavior and corresponding engine/runtime tests
- Document manual PR branch conventions and follow-up behavior in task management and dashboard docs

Fusion-Task-Id: FN-3202
This commit is contained in:
Fusion
2026-05-02 10:59:51 -07:00
committed by gsxdsm
parent 7cab64e346
commit 656df5de29
9 changed files with 174 additions and 14 deletions
Download Patch File Download Diff File Expand all files Collapse all files

8
docs/task-management.md
View File

@@ -250,12 +250,18 @@ fn task import owner/repo --labels bug --limit 20
fn task import owner/repo --interactive
```
Create PR for in-review task:
Create PR for an `in-review` task:
```bash
fn task pr-create FN-120 --title "Fix flaky auth flow" --base main
```
Manual/non-auto-merge behavior:
- Task PR branches use `fusion/<task-id-lower>`.
- Manual PR creation first checks for an existing PR on that branch and links it when found.
- If no PR exists, Fusion pushes the task branch to `origin` before creating the PR.
- When buffered actionable PR feedback exists on a PR that is already merged/closed and the task leaves `in-review`, Fusion creates a dependency-linked follow-up task in `triage` so feedback is not stranded.
## Completion Modes (`mergeStrategy`)
- **`direct`**: local squash-merge flow into target branch