Conversation
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/59004734-167f-45e6-9c57-88a381ba24e7 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/59004734-167f-45e6-9c57-88a381ba24e7 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
assign_to_agent output field name from issue-number to issue_numberissue_number for assign_to_agent and soften assignment comment wording
|
Hey The PR is focused on a single bug, ships with a regression guard test, and has a clear description covering both the root cause and the fix. It looks ready for maintainer review. 🎉
|
| @@ -0,0 +1,24 @@ | |||
| //go:build !integration | |||
There was a problem hiding this comment.
Done — I removed pkg/cli/issue_monster_workflow_test.go in commit a26f97a.
Agent-Logs-Url: https://github.com/github/gh-aw/sessions/bbbf5589-7bca-4ddc-b6f0-5527482f5923 Co-authored-by: pelikhan <4175913+pelikhan@users.noreply.github.com>
|
Just as a heads up, I was blocked by some firewall rules while working on your feedback. Expand below for details. Warning Firewall rules blocked me from connecting to one or more addresses (expand for details)I tried to connect to the following addresses, but was blocked by firewall rules:
If you need me to access, download, or install something from one of these locations, you can either:
|
There was a problem hiding this comment.
Pull request overview
Updates the Issue Monster workflow prompt to ensure assign_to_agent uses a safe-output-valid parameter name and to avoid posting misleading “assignment succeeded” messaging.
Changes:
- Clarifies that
safeoutputs/assign_to_agentmust be called withissue_number(underscore) and explicitly warns againstissue-number(hyphen). - Softens the issue comment template wording from “assigned” to “requested assignment” to avoid false-positive messaging.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/issue-monster.md |
Tightens the prompt contract for assign_to_agent and updates the comment template to reflect that assignment may fail. |
Copilot's findings
Tip
Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
- Files reviewed: 1/1 changed files
- Comments generated: 1
| ``` | ||
| safeoutputs/add_comment(item_number=<issue_number>, body="🍪 **Issue Monster has assigned this to Copilot!**\n\nI've identified this issue as a good candidate for automated resolution and assigned it to the Copilot coding agent.\n\nThe Copilot coding agent will analyze the issue and create a pull request with the fix.\n\nOm nom nom! 🍪") | ||
| safeoutputs/add_comment(item_number=<issue_number>, body="🍪 **Issue Monster selected this for Copilot!**\n\nI've identified this issue as a good candidate for automated resolution and requested assignment to the Copilot coding agent.\n\nIf assignment succeeds, the Copilot coding agent will analyze the issue and create a pull request with the fix.\n\nOm nom nom! 🍪") | ||
| ``` |
There was a problem hiding this comment.
The comment template now correctly avoids claiming assignment success ("requested assignment" / "If assignment succeeds"), but the surrounding instruction text still frames this as "Add Comment to Each Assigned Issue" / "For each issue you assign". Consider aligning that wording to "requested" or "attempted" assignment to avoid confusing agents about whether they should comment even when assignment fails.
Issue Monster was emitting
assign_to_agentoutputs withissue-number(hyphen), which fails safe-output validation and prevents actual Copilot assignment. It also posted comments claiming assignment success even when assignment could fail.Prompt contract correction (
issue-monster.md)issue_number(underscore) forsafeoutputs/assign_to_agent(...).issue-number.Comment semantics update (
issue-monster.md)> [!WARNING]
>
>