Review GitHub issue-agent changes before they apply

GitHub Issues now has a practical review layer for agent-driven triage. It is useful if you let Copilot cloud agent or GitHub Agentic Workflows label, assign, type, close, or update issue fields and want fewer unexplained changes in busy repositories.

What it is

GitHub added rationale, confidence, and approvals for supported issue automation actions. Agents can attach a reason to a change, rate confidence as high, medium, or low, and leave lower-confidence actions as suggestions instead of applying them immediately.

Who it helps

Maintainers, support teams, and product squads that use issue automation can use this to keep triage fast without making every metadata change invisible. It is especially relevant for public repositories, large backlogs, and workflows where spam detection, priority labels, or owner assignment need review.

How to evaluate it

Start with one workflow that touches low-risk fields such as labels or issue type. In GitHub Agentic Workflows, GitHub says issue intents are optional and enabled by default, and can be required per safe output. For Copilot cloud agent, GitHub says no update is needed; test from the Automations pane in the repository Agents tab.

Use has:suggestions in issue search to find pending review items, then compare agent rationale against your existing triage rules.

Limits and risks

GitHub explicitly says approvals are a workflow convenience, not a security control. They do not create a server-side permission boundary, and an agent with permission to change issues can still apply changes directly if configured to do so. Treat this as observability and review UX, not a substitute for least-privilege access.

Sources

• GitHub changelog
• GitHub Docs: rationale, confidence, and approvals