fix/emtpy-loging #1

Merged
Latte merged 4 commits from fix/emtpy-loging into main 2026-01-16 12:18:27 +00:00
5 changed files with 314 additions and 0 deletions
Showing only changes of commit b30a44d376 - Show all commits

View File

@@ -0,0 +1,61 @@
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
name: AI Chat (Bartender)
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# WORKFLOW ROUTING:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# This workflow handles FREE-FORM questions/chat (no specific command)
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# Other workflows: ai-issue-triage.yml (@codebot triage), ai-comment-reply.yml (specific commands)
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# This is the FALLBACK for any @codebot mention that isn't a known command
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
on:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
issue_comment:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
types: [created]
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# CUSTOMIZE YOUR BOT NAME:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# Change '@codebot' in all conditions below to match your config.yml mention_prefix
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# Examples: '@bartender', '@uni', '@joey', '@codebot'
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
jobs:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
ai-chat:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# Only run if comment mentions the bot but NOT a specific command
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# This prevents duplicate runs with ai-comment-reply.yml and ai-issue-triage.yml
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
# CRITICAL: Ignore bot's own comments to prevent infinite loops (bot username: Bartender)
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
if: |
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
github.event.comment.user.login != 'Bartender' &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
contains(github.event.comment.body, '@codebot') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot triage') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot help') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot explain') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot suggest') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot security') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot summarize') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot changelog') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot explain-diff') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot review-again') &&
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
!contains(github.event.comment.body, '@codebot setup-labels')
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
runs-on: ubuntu-latest
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
steps:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
- uses: actions/checkout@v4
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
- uses: actions/checkout@v4
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
with:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
repository: Hiddenden/openrabbit
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
path: .ai-review
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
token: ${{ secrets.AI_REVIEW_TOKEN }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
- uses: actions/setup-python@v5
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
with:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
python-version: "3.11"
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
- run: pip install requests pyyaml
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
- name: Run AI Chat
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
env:
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
AI_REVIEW_REPO: ${{ gitea.repository }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
SEARXNG_URL: ${{ secrets.SEARXNG_URL }}
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
run: |
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
cd .ai-review/tools/ai-review
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.
python main.py comment ${{ gitea.repository }} ${{ gitea.event.issue.number }} "${{ gitea.event.comment.body }}"
Review

[LOW] Security

The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection.

Recommendation: Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

**[LOW] Security** The workflow uses secrets for tokens and API keys correctly, but the workflow runs on all issue comments mentioning the bot without rate limiting or abuse protection. **Recommendation:** Consider adding rate limiting or abuse detection mechanisms to prevent potential denial-of-service or spam via bot mentions.

View File

@@ -0,0 +1,58 @@
name: AI Codebase Quality Review
on:
# # Weekly scheduled run
# schedule:
# - cron: "0 0 * * 0"
# Manual trigger
workflow_dispatch:
inputs:
report_type:
description: "Type of report to generate"
required: false
default: "full"
type: choice
options:
- full
- security
- quick
jobs:
ai-codebase-review:
runs-on: ubuntu-latest
steps:
# Checkout the repository
- uses: actions/checkout@v4
with:
fetch-depth: 0 # Full history for analysis
# Checkout central AI tooling
- uses: actions/checkout@v4
with:
repository: Hiddenden/openrabbit
path: .ai-review
token: ${{ secrets.AI_REVIEW_TOKEN }}
# Setup Python
- uses: actions/setup-python@v5
with:
python-version: "3.11"
# Install dependencies
- run: pip install requests pyyaml
# Run AI codebase analysis
- name: Run AI Codebase Analysis
env:
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
AI_REVIEW_REPO: ${{ gitea.repository }}
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
run: |
cd .ai-review/tools/ai-review
python main.py codebase ${{ gitea.repository }}

View File

@@ -0,0 +1,98 @@
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
name: AI Comment Reply
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# WORKFLOW ROUTING:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# This workflow handles SPECIFIC commands: help, explain, suggest, security, summarize, changelog, explain-diff, review-again, setup-labels
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Other workflows: ai-issue-triage.yml (@codebot triage), ai-chat.yml (free-form questions)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
on:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
issue_comment:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
types: [created]
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# CUSTOMIZE YOUR BOT NAME:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Change '@codebot' in the 'if' condition below to match your config.yml mention_prefix
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Examples: '@bartender', '@uni', '@joey', '@codebot'
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
jobs:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
ai-reply:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
runs-on: ubuntu-latest
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Only run for specific commands (not free-form chat or triage)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# This prevents duplicate runs with ai-chat.yml and ai-issue-triage.yml
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# CRITICAL: Ignore bot's own comments to prevent infinite loops (bot username: Bartender)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
if: |
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
github.event.comment.user.login != 'Bartender' &&
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
(contains(github.event.comment.body, '@codebot help') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot explain') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot suggest') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot security') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot summarize') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot changelog') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot explain-diff') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot review-again') ||
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
contains(github.event.comment.body, '@codebot setup-labels'))
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
steps:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
- uses: actions/checkout@v4
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
- uses: actions/checkout@v4
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
with:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
repository: Hiddenden/openrabbit
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
path: .ai-review
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
token: ${{ secrets.AI_REVIEW_TOKEN }}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
- uses: actions/setup-python@v5
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
with:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
python-version: "3.11"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
- run: pip install requests pyyaml
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
- name: Run AI Comment Response
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
env:
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
run: |
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
cd .ai-review/tools/ai-review
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Determine if this is a PR or issue comment
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
IS_PR="${{ gitea.event.issue.pull_request != null }}"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
REPO="${{ gitea.repository }}"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
ISSUE_NUMBER="${{ gitea.event.issue.number }}"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Validate inputs
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
if [ -z "$REPO" ] || [ -z "$ISSUE_NUMBER" ]; then
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
echo "Error: Missing required parameters"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
exit 1
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
fi
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Validate repository format (owner/repo)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
if ! echo "$REPO" | grep -qE '^[a-zA-Z0-9_-]+/[a-zA-Z0-9_-]+$'; then
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
echo "Error: Invalid repository format: $REPO"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
exit 1
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
fi
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
if [ "$IS_PR" = "true" ]; then
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# This is a PR comment - use safe dispatch with minimal event data
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Build minimal event payload (does not include sensitive user data)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
EVENT_DATA=$(cat <<EOF
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
{
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"action": "created",
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"issue": {
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"number": ${{ gitea.event.issue.number }},
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"pull_request": {}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
},
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"comment": {
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"id": ${{ gitea.event.comment.id }},
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
"body": $(echo '${{ gitea.event.comment.body }}' | jq -Rs .)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
}
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
EOF
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
)
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# Use safe dispatch utility
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
python utils/safe_dispatch.py issue_comment "$REPO" "$EVENT_DATA"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
else
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
# This is an issue comment - use the comment command
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
COMMENT_BODY='${{ gitea.event.comment.body }}'
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
python main.py comment "$REPO" "$ISSUE_NUMBER" "$COMMENT_BODY"
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.
fi
Review

[LOW] Correctness

The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters.

Recommendation: Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

**[LOW] Correctness** The shell script uses 'grep -qE' to validate repository format but does not handle cases where repository names might include dots or other valid characters. **Recommendation:** Expand the regex to allow valid repository name characters such as dots ('.') and ensure it matches all valid GitHub/Gitea repo name formats.

View File

@@ -0,0 +1,44 @@
name: AI Issue Triage
# WORKFLOW ROUTING:
# This workflow handles ONLY the 'triage' command
# Other workflows: ai-comment-reply.yml (specific commands), ai-chat.yml (free-form questions)
on:
issue_comment:
types: [created]
jobs:
ai-triage:
runs-on: ubuntu-latest
# Only run if comment contains @codebot triage
# CRITICAL: Ignore bot's own comments to prevent infinite loops (bot username: Bartender)
if: |
github.event.comment.user.login != 'Bartender' &&
contains(github.event.comment.body, '@codebot triage')
steps:
- uses: actions/checkout@v4
- uses: actions/checkout@v4
with:
repository: Hiddenden/openrabbit
path: .ai-review
token: ${{ secrets.AI_REVIEW_TOKEN }}
- uses: actions/setup-python@v5
with:
python-version: "3.11"
- run: pip install requests pyyaml
- name: Run AI Issue Triage
env:
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
AI_REVIEW_REPO: ${{ gitea.repository }}
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
run: |
cd .ai-review/tools/ai-review
python main.py issue ${{ gitea.repository }} ${{ gitea.event.issue.number }}

View File

@@ -0,0 +1,53 @@
name: Enterprise AI Code Review
on:
pull_request:
types: [opened, synchronize]
jobs:
ai-review:
runs-on: ubuntu-latest
steps:
# Checkout the PR repository
- uses: actions/checkout@v4
with:
fetch-depth: 0
# Checkout the CENTRAL AI tooling repo
- uses: actions/checkout@v4
with:
repository: Hiddenden/openrabbit
path: .ai-review
token: ${{ secrets.AI_REVIEW_TOKEN }}
# Setup Python
- uses: actions/setup-python@v5
with:
python-version: "3.11"
# Install dependencies
- run: pip install requests pyyaml
# Run the AI review
- name: Run Enterprise AI Review
env:
AI_REVIEW_TOKEN: ${{ secrets.AI_REVIEW_TOKEN }}
AI_REVIEW_REPO: ${{ gitea.repository }}
AI_REVIEW_API_URL: https://git.hiddenden.cafe/api/v1
AI_REVIEW_PR_NUMBER: ${{ gitea.event.pull_request.number }}
OPENAI_API_KEY: ${{ secrets.OPENAI_API_KEY }}
OPENROUTER_API_KEY: ${{ secrets.OPENROUTER_API_KEY }}
OLLAMA_HOST: ${{ secrets.OLLAMA_HOST }}
run: |
cd .ai-review/tools/ai-review
python main.py pr ${{ gitea.repository }} ${{ gitea.event.pull_request.number }} \
--title "${{ gitea.event.pull_request.title }}"
# Fail CI on HIGH severity (optional)
- name: Check Review Result
if: failure()
run: |
echo "AI Review found HIGH severity issues. Please address them before merging."
exit 1