can1357
f18eb90324
- Added `is_implementation_authorizer` check requiring OWNER or allowlisted maintainer to authorize implementation work. - Blocked `gh_push_branch` and `gh_open_pr` for unclassified/enhancement/proposal issues without explicit directive authorization. - Auto-allowed bug and documentation issues without requiring a directive. - Propagated `authorizes_impl` flag through events, server, tasks, and worker bindings.
878 B
878 B
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. - 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.