Skip to content

docs(lfg): align leftover-findings FAQ with PR-body checklist #1582

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
tmchow merged 1 commit into from
Aug 31, 2026
+1 −1
Merged

docs(lfg): align leftover-findings FAQ with PR-body checklist #1582

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
2 changes: 1 addition & 1 deletion docs/guides/lfg.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -211,7 +211,7 @@ No. That is the point of the skill, and why it is the wrong tool for in-the-loop
The pipeline stops. Non-software tasks, requirements-only leftovers, knowledge-work plans, and invalidating settlement conflicts all halt before implementation.

**Where do leftover review findings go?**
Not into the PR description. They are filed in the project tracker when possible, and carried in one run-report comment on the PR.
They are listed as an `## Unapplied review findings` checklist in the PR body for the reviewer to decide on: fix in-branch, dismiss, or file a ticket. `lfg` files tickets itself only when no PR will exist.

**What happens if there is no `origin`?**
Local commits only. No push, no PR, no CI watch.
Expand Down