🔧 Troubleshooting: Reviewer Did Not Run
✅ Quick Checklist
Before diving deeper, verify the basics:
- 📄 The workflow file exists at
.gitea/workflows/kodo-reviewer.yaml - 🔑 The secrets
CC_GITEATOKENandCC_API_KEYare set in the repository settings by thedevopsteam - 🖥️ The runner
kodo-reviewis online and available - 🏷️ The PR title does not contain
[no ai]
🔍 Common Causes & Fixes
PR title contains [no ai]
The action checks for [no ai] in the PR title and skips execution if found.
Fix: Remove [no ai] from the PR title and push a new commit or re-open the PR.
⚙️ Issues with Git Extensions (e.g., Git LFS)
Q: Why does my pipeline fail when using Git extensions like Git LFS?
A: Our image includes a standard Git installation, but additional Git extensions such as Git LFS are not bundled, as the AI reviewer is designed to work with small, standard code files and does not need to process large files.
However, some extensions (like Git LFS) hook directly into Git at a low level, which can cause errors even if the reviewer never touches the large files themselves.
Example: Git LFS
If your repository uses Git LFS, the extension may interfere with the standard Git in our image and cause the review step to fail. The correct solution is to explicitly disable LFS for the review step:
clone:
depth: full
lfs: false
script:
- export GIT_LFS_SKIP_SMUDGE=1
You do not need to install LFS into the image — disabling it for this step is the recommended approach.
Q: Can I install a Git extension directly into the image?
A: Technically yes, but it is not recommended. The reviewer is optimized for small, typical code repository files. Installing heavy extensions adds unnecessary overhead and is outside the intended use case.
Summary: If you encounter Git extension-related errors, check whether the extension is hooking into Git globally and disable it explicitly for the review step.
📨 Still Not Working?
Provide the following information when asking for help from devops team:
- Runner name and status (
kodo-review) - Workflow run URL
- Event that was expected to trigger the review
- Observed and expected behavior
🤖 Kodo AI Reviewer
📚 Gitea
👩💻 Developer
🧑🔧 Tech Lead
- CI/CD Integration
- Extension of Existing Review Rules
- Overriding Review Rules
- Troubleshooting
- Configuration and Parameters
📚 Bitbucket
👩💻 Developer
🧑🔧 Tech Lead
- CI/CD Integration
- Extension of Existing Review Rules
- Overriding Review Rules
- Troubleshooting
- Configuration and Parameters