can1357
79faf94f26
- Added `wontfix` to primary classification handling by updating host-tool classification metadata and issue taxonomy prompts. - Updated kickoff/follow-up/system prompt guidance to treat intentional-design reports as `wontfix`, with maintainer-intent signals stopping work and ending in a single explanatory comment. - Added tests to verify `classify_issue` persists a `wontfix` classification and returns a no-PR, comment-only next step.
1.2 KiB
1.2 KiB
Follow-up on {{repo.full_name}}#{{inbound.number}} ({{inbound.kind}})
Thread context: {{origin.description}}. PR state: {{state.pr_status}}.
Prior conversation
{{thread}}
New comment by @{{comment.author}} ({{comment.created_at}})
{{comment.body}}
Decide what to do:
- New repro info? Re-run via
repro_record, thengh_post_commentwith the outcome. - Maintainer dismissal? A maintainer saying "intended", "not an issue", "works as designed", or similar — however terse — permanently ends the fix workflow. No further commits, pushes, or PRs, even mid-fix with work already done. Apply
wontfixviaset_issue_labels(when available on this thread), reply with at most one short acknowledgement, and stop. - PR change requested? Amend
{{workspace.branch}}and push only for an already-open PR / authorized implementation; NEVER open a second PR, and NEVER open the first PR for an unauthorized enhancement/proposal. Reply with a shortgh_post_commentnaming what changed. - Confirmation or unrelated question? Reply with one
gh_post_comment. Leave code untouched. - Bot author or no actionable content? No-op.
You MUST reuse the recorded session state. NEVER restart from scratch.