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

feat(FN-840): add closed/merged PR feedback contract and clean up unused code

Browse Source 
- Add closed/merged PR feedback contract to pr-monitor for post-merge follow-up behavior
- Fix PR monitor drainComments + consume/drain behavior with comprehensive tests
- Add PR feedback follow-up tests and scheduler follow-up logic
- Remove unused activity log, agent log viewer, and multi-agent log code from dashboard
- Remove unused store methods, types, API endpoints, and route handlers
- Update README docs to document manual-merge PR follow-up behavior and fix auth wording
- Add dashboard CLI test coverage for new commands
This commit is contained in:
gsxdsm
2026-04-04 02:01:58 -07:00
parent e2720edfb1
commit 574d1793fc
7 changed files with 416 additions and 10 deletions
Download Patch File Download Diff File Expand all files Collapse all files

10
README.md
View File

@@ -540,12 +540,16 @@ Fusion supports two completion strategies once a task reaches **In Review**:
PR-first automation is designed for repositories that require GitHub-side governance:
- Authenticate GitHub access with `gh auth login` or `GITHUB_TOKEN`
- Authenticate GitHub access with `gh auth login` (the `gh` CLI is required for PR monitoring and badge updates)
- Ensure the task branch already exists on GitHub using the normal fusion branch naming convention: `fusion/<task-id-lower>`
- Expect the task to remain in **In Review** while required checks are pending/failing or a review is blocking merge
**Important:** Fusion does **not** implicitly push task branches before creating a PR. PR-first mode assumes branch publishing is handled by your existing workflow or repository automation.
#### Manual merge (`autoMerge=false`)
When `autoMerge` is off and a task's PR is closed or merged, Fusion checks for unaddressed review feedback that was collected while the PR was open. If actionable comments were left by reviewers, Fusion automatically creates a follow-up task in **Triage** depending on the original task. This ensures PR feedback is never silently dropped even when automatic merging is disabled.
### Spec Editing & AI Revision
The dashboard includes a **Spec** tab for managing task specifications directly in the UI:
@@ -573,9 +577,9 @@ When a task has a linked PR, Fusion automatically monitors it for new review com
- **Adaptive polling**: Checks every 30 seconds when active, 5 minutes when idle
- **Actionable feedback detection**: Filters out "LGTM" and "Thanks" comments, detects requests like "fix", "change", "update"
- **Steering comments**: Automatically adds actionable review feedback as steering comments on the task
- **Follow-up tasks**: When a PR is closed with unaddressed feedback, a follow-up task is created
- **Follow-up tasks**: When a PR is closed or merged with unaddressed feedback, a follow-up task is created in Triage
Uses `gh` CLI authentication when available, falls back to `GITHUB_TOKEN` if set.
Requires `gh` CLI installed and authenticated (`gh auth login`). PR monitoring does not support `GITHUB_TOKEN` as a fallback.
## Task Comments vs Steering Comments