Summary
When an agentic workflow is triggered by a slash_command, the harness provides rich in-issue feedback:
activation job — an "Add comment with workflow run link" step posts a "processing…" comment on the issue and captures its ID (steps.add-comment.outputs.comment-id).conclusion job — an "Update reaction comment with completion status" step updates that comment with the final result (success / failure / cancelled).
When triggered by issues: labeled, neither of these steps exists. The activation job hardcodes comment_id: "", so the entire run is invisible to anyone watching the issue — the only place to see what happened is the Actions log.
Desired behavior
Add equivalent steps to workflows compiled for the issues: labeled trigger:
- In
activation: post an initial comment on the labeled issue linking to the workflow run, capture its ID.
- In
conclusion: update that comment with the completion status, mirroring the slash_command conclusion step.
The overall experience (from the perspective of a user who added a label) should be comparable to triggering a slash_command: you see the agent acknowledge the event and report back when it's done.
Notes
- The label event itself does not produce a GitHub comment, so a synthetic one must be created (same pattern as slash_command activation).
- The
comment_repo output would be the repository where the label was applied (github.event.repository.full_name for same-repo triggers, or the dispatching repo for repository_dispatch variants).
Filed by Claude Code on behalf of a workflow author.
Summary
When an agentic workflow is triggered by a
slash_command, the harness provides rich in-issue feedback:activationjob — an "Add comment with workflow run link" step posts a "processing…" comment on the issue and captures its ID (steps.add-comment.outputs.comment-id).conclusionjob — an "Update reaction comment with completion status" step updates that comment with the final result (success / failure / cancelled).When triggered by
issues: labeled, neither of these steps exists. Theactivationjob hardcodescomment_id: "", so the entire run is invisible to anyone watching the issue — the only place to see what happened is the Actions log.Desired behavior
Add equivalent steps to workflows compiled for the
issues: labeledtrigger:activation: post an initial comment on the labeled issue linking to the workflow run, capture its ID.conclusion: update that comment with the completion status, mirroring the slash_command conclusion step.The overall experience (from the perspective of a user who added a label) should be comparable to triggering a slash_command: you see the agent acknowledge the event and report back when it's done.
Notes
comment_repooutput would be the repository where the label was applied (github.event.repository.full_namefor same-repo triggers, or the dispatching repo forrepository_dispatchvariants).Filed by Claude Code on behalf of a workflow author.