[Copilot]

This adds a GitHub Agentic Workflow to triage newly opened issues. The workflow classifies issues by type and priority, detects likely duplicates, asks for missing information when reports are underspecified, and routes actionable issues to the repository owner.

• Workflow

  • Adds .github/workflows/issue-triage.md as the source workflow for issues.opened
  • Enables community-triggered issue triage with roles: all
  • Keeps the agent job read-only and routes mutations through safe outputs

• Triage actions

  • Maps issues to GitHub issue types: Bug, Feature, or Task
  • Applies repository labels from the existing taxonomy: bug, enhancement, documentation, question, and duplicate
  • Sets the org-level Priority field to Urgent, High, Medium, or Low

• Routing and duplicate handling

  • Assigns actionable non-duplicate issues to JanuszNowak
  • Closes only high-confidence duplicates after labeling and posting a canonical reference
  • Leaves ambiguous or incomplete issues open and asks the minimum clarifying questions needed for follow-up

• Compiled workflow artifacts

  • Adds the compiled lock file consumed by GitHub Actions
  • Marks *.lock.yml workflow artifacts as generated in .gitattributes

on:
  issues:
    types: [opened]
  roles: all

safe-outputs:
  add-labels:
    allowed: [bug, enhancement, documentation, question, duplicate]
  set-issue-type:
    allowed: [Bug, Feature, Task]
  set-issue-field:
    allowed-fields: [Priority]
  assign-to-user:
    allowed: [JanuszNowak]
  close-issue:
    state-reason: [duplicate]

[Copilot]

🟡 Changes recommended

Unresolved security, validation, duplicate-detection, and clarification-path issues must be addressed.

Get a fresh assessment by requesting another Copilot review.

Pull request overview

Adds an agentic workflow to triage newly opened issues through classification, labeling, prioritization, duplicate detection, clarification, and routing.

Changes:

• Adds source and compiled workflow artifacts.
• Constrains issue mutations through safe outputs.
• Marks compiled lock files as generated.

File summaries

File	Summary
.github/workflows/issue-triage.md	Defines triage behavior and guardrails; unresolved issues remain around output targeting, duplicate pagination, priority validation, and clarification handling.
.github/workflows/issue-triage.lock.yml	Compiled workflow artifact consumed by GitHub Actions.
.gitattributes	Marks compiled workflow lock files as generated.

Review details

Suppressed comments (3)

.github/workflows/issue-triage.md:102

• This guardrail conflicts with the required clarification branch above: an underspecified issue is also likely to be judged as having insufficient evidence to act safely, so the agent can call noop and skip the question label and clarifying comment. That would defeat the workflow's stated missing-information behavior; limit noop to already-triaged cases and direct incomplete-but-safe reports to the clarification branch.

- If the issue is already clearly triaged or there is not enough evidence to act safely, call `noop` with a short reason.

.github/workflows/issue-triage.md:85

• The PR description promises that only high-confidence duplicates are closed, but this branch only says “true duplicate,” and the generated close_issue schema accepts an optional confidence without requiring HIGH. A merely overlapping issue could therefore be closed. Require strong evidence and confidence: HIGH for the close output; otherwise leave the issue open and use noop.

- If the issue is a true duplicate:
  - add the `duplicate` label
  - post a short comment that links to the canonical issue and explains the overlap
  - close the triggering issue as a duplicate of that canonical issue

.github/workflows/issue-triage.md:31

• allowed-fields only constrains the field name; the compiled validation leaves value as an arbitrary string. The agent can therefore emit a value outside Urgent, High, Medium, or Low, causing the write to fail or storing a value outside the policy. Add an allowed-value validation or post-processing check for those four options before applying this output.

  set-issue-field:
    allowed-fields: [Priority]

• Files reviewed: 2/3 changed files
• Comments generated: 2
• Review effort level: Lite

---

💡 Add a code-review agent skill or configure MCP servers for context-aware, tailored reviews. Learn more in the docs.

[sonarqubecloud]

Quality Gate passed

Issues
0 New issues
0 Accepted issues

Measures
0 Security Hotspots
0.0% Coverage on New Code
0.0% Duplication on New Code

See analysis details on SonarQube Cloud