Repository navigation
feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow - #284
Conversation
|
Warning Rate limit exceeded
You’ve run out of usage credits. Purchase more in the billing tab. ⌛ How to resolve this issue?After the wait time has elapsed, a review can be triggered using the We recommend that you space out your commits to avoid hitting the rate limit. 🚦 How do rate limits work?CodeRabbit enforces hourly rate limits for each developer per organization. Our paid plans have higher rate limits than the trial, open-source and free plans. In all cases, we re-allow further reviews after a brief timeout. Please see our FAQ for further information. ℹ️ Review info⚙️ Run configurationConfiguration used: Organization UI Review profile: ASSERTIVE Plan: Pro Run ID: 📒 Files selected for processing (1)
📝 WalkthroughWalkthroughAdds an issue triage agentic workflow that automatically classifies new GitHub issues, selects up to three labels from an allowed set, and posts a single clarifying question, skipping issues already labeled. Includes a CLI tool for compiling and executing workflows, a two-job GitHub Actions runner with read-only triage and write-enabled apply stages, test scenarios and fixtures, validation tests, and documentation. ChangesIssue Triage Agentic Workflow
Estimated code review effort🎯 4 (Complex) | ⏱️ ~45 minutes 🚥 Pre-merge checks | ✅ 4 | ❌ 1❌ Failed checks (1 warning)
✅ Passed checks (4 passed)
✏️ Tip: You can configure your own custom pre-merge checks in the settings. ✨ Finishing Touches🧪 Generate unit tests (beta)
Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out. Comment |
Dev-Lead — human-pr (no-changes)No changes were needed for this PR. |
Dev-Lead — fix-bot-comment (applied)Changes committed and pushed. |
There was a problem hiding this comment.
Code Review
This pull request introduces an automated "Issue Triage" agentic workflow, including a CLI tool for validation and execution, comprehensive documentation, and test scenarios. The workflow uses Claude to classify GitHub issues and apply labels or comments based on predefined rules. Review feedback identifies several critical issues in the aw.sh script, most notably a high-severity code injection vulnerability caused by direct variable interpolation into Python source code. Other feedback points out incorrect label formatting for the GitHub CLI, potential system argument limit issues when posting large comments, and opportunities to improve the security and efficiency of fixture parsing.
There was a problem hiding this comment.
Pull request overview
Note
Copilot was unable to run its full agentic suite in this review.
Adds a new "Issue Triage" GitHub Agentic Workflow (Phase 1 of #232): a workflow definition, a runner, a generic gh aw CLI shell script, scenario spec, docs, and a CI compile check.
Changes:
- New
issue-triageworkflow definition (.github/workflows/issue-triage.md) plus a two-job runner that stages Claude output and applies it viasafe-output. - New
scripts/aw.shCLI implementingcompile,run, andsafe-output applysubcommands. - Docs, scenario spec, and a
aw-compileCI job to validate workflow definitions.
Reviewed changes
Copilot reviewed 6 out of 6 changed files in this pull request and generated 16 comments.
Show a summary per file
| File | Description |
|---|---|
.github/workflows/issue-triage.md |
Workflow frontmatter + Claude triage prompt template. |
.github/workflows/issue-triage-runner.yml |
Actions runner: triage (read) → apply (write), bridged via base64-encoded JSON output. |
scripts/aw.sh |
gh aw CLI: compile/validate, run (with skip guard + Claude invocation), safe-output apply. |
.github/workflows/test.yml |
Adds aw-compile job running aw.sh compile --all in CI. |
docs/aw/issue-triage.md |
User-facing docs for the workflow. |
tests/aw/issue-triage/scenarios.md |
Behavioural scenario spec (bug / feature / question / already-labelled). |
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
Dev-Lead Fix CI — appliedPR: #284 | SHA: |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 961e1cc525
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
No description provided. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: 568b293bdb
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a563cc706e
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
|
@dev-lead - please fix this PR |
Dev-Lead — human (applied)Changes committed and pushed. |
There was a problem hiding this comment.
💡 Codex Review
Here are some automated review suggestions for this pull request.
Reviewed commit: a95a13fbff
ℹ️ About Codex in GitHub
Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you
- Open a pull request for review
- Mark a draft as ready
- Comment "@codex review".
If Codex has suggestions, it will comment; otherwise it will react with 👍.
Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".
There was a problem hiding this comment.
Actionable comments posted: 4
Caution
Some comments are outside the diff and can’t be posted inline due to platform limitations.
⚠️ Outside diff range comments (1)
.github/workflows/issue-triage-runner.yml (1)
1-71:⚠️ Potential issue | 🟠 Major | ⚡ Quick winUse the required workflow template verbatim.
This workflow appears to be custom-authored rather than a verbatim template from
standards/workflows/, which violates repo workflow policy.As per coding guidelines, ".github/workflows/**/*.yml: All workflow changes must use templates from
standards/workflows/verbatim without modification".🤖 Prompt for AI Agents
Verify each finding against current code. Fix only still-valid issues, skip the rest with a brief reason, keep changes minimal, and validate. In @.github/workflows/issue-triage-runner.yml around lines 1 - 71, This workflow ("name: Issue Triage", jobs: triage and apply) must be replaced with the exact verbatim template from standards/workflows/issue-triage-runner.yml; do not keep custom edits (e.g., the anthropics/claude-code-action setup step, custom pip install/run blocks, or modified actions/checkout ref) — fetch the canonical template and copy its contents exactly into this file so the workflow matches the required template bit-for-bit, preserving the template's job names (triage, apply) and steps as-is.
🤖 Prompt for all review comments with AI agents
Verify each finding against current code. Fix only still-valid issues, skip the
rest with a brief reason, keep changes minimal, and validate.
Inline comments:
In @.github/workflows/issue-triage-runner.yml:
- Line 20: Update the two actions/checkout steps that currently use
actions/checkout@de0fac2e4500dabe0009e67214ff5f5447ce83dd to set
persist-credentials: false so the checkout action does not pass the GITHUB_TOKEN
to later steps; locate the checkout invocations (the two places calling
actions/checkout) and add the persist-credentials: false input under each
checkout step.
- Line 28: Update both CI job steps that run "pip install pyyaml --quiet" (the
triage and apply job run steps) to pin PyYAML to a safe version; replace the
unpinned install with a pinned spec such as "pip install pyyaml==6.0.3 --quiet"
(or at minimum "pyyaml>=5.4") to ensure deterministic, vulnerability-patched
dependency resolution for the triage and apply job run commands.
In @.github/workflows/test.yml:
- Line 31: The pip install step currently runs "pip install pyyaml --quiet"
which lacks version pinning and the --only-binary flag; update that workflow
step (the run: pip install ... command in the GitHub Actions job) to pin pyyaml
to a specific safe version (e.g., ==6.0.2 or another vetted stable release) and
add --only-binary :all: to prevent execution of package setup scripts during
install.
- Line 28: The workflow uses an unpinned third-party action "uses:
actions/checkout@v6" which violates the policy; update both occurrences (the one
shown and the one in the unit-tests job) to pin the action to a specific commit
SHA by replacing the tag reference with the full commit hash for
actions/checkout (e.g., actions/checkout@<commit-sha>) so the workflow
references an immutable revision and satisfies the blanket policy.
---
Outside diff comments:
In @.github/workflows/issue-triage-runner.yml:
- Around line 1-71: This workflow ("name: Issue Triage", jobs: triage and apply)
must be replaced with the exact verbatim template from
standards/workflows/issue-triage-runner.yml; do not keep custom edits (e.g., the
anthropics/claude-code-action setup step, custom pip install/run blocks, or
modified actions/checkout ref) — fetch the canonical template and copy its
contents exactly into this file so the workflow matches the required template
bit-for-bit, preserving the template's job names (triage, apply) and steps
as-is.
🪄 Autofix (Beta)
Fix all unresolved CodeRabbit comments on this PR:
- Push a commit to this branch (recommended)
- Create a new PR with the fixes
ℹ️ Review info
⚙️ Run configuration
Configuration used: Organization UI
Review profile: ASSERTIVE
Plan: Pro
Run ID: ab0e7c2c-33a0-468e-b65f-b993f2e8d6e2
📒 Files selected for processing (9)
.github/workflows/issue-triage-runner.yml.github/workflows/issue-triage.md.github/workflows/test.ymldocs/aw/issue-triage.mdscripts/aw.shtests/aw/issue-triage/fixtures/scenario-1-bug.jsontests/aw/issue-triage/fixtures/scenario-4-skip.jsontests/aw/issue-triage/scenarios.mdtests/aw/issue-triage/test_aw_run.sh
|
@coderabbitai resolve |
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
* feat: implement issue #232 — Phase 1: Issue Triage gh-aw workflow * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(reviews): address review comments [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(bot): address bot feedback [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * fix(ci): auto-fix for SonarCloud Code Analysis [skip ci-relay] * chore: apply manual instructions [skip ci-relay] * chore: sync ci.yml with main to resolve merge conflict * chore: sync test.yml with main to resolve merge conflict * fix(aw): remove 'name' field from issue-triage.md frontmatter (not allowed in gh-aw) * fix(aw): correct issue-triage.md frontmatter for gh-aw schema (on:, safe-outputs) * fix(aw): use minimal valid gh-aw frontmatter for issue-triage.md * fix(aw): use correct add-labels schema in issue-triage.md * fix(aw): remove stale frontmatter from body of issue-triage.md * fix(aw): clean up issue-triage.md — remove duplicate frontmatter from body --------- Co-authored-by: donpetry-bot <donpetry-bot@users.noreply.github.com>
Closes #232
Implemented by dev-lead agent. Please review.
Summary by CodeRabbit
New Features
Documentation
Tests
Chores