Add HTTP response status checking to all Gitea tracker methods that were silently swallowing errors
Add fallback in create_pr_review: if inline comments fail, retry as plain PR comment
Test plan
Deploy and trigger a PR review, check logs for actual error details
Verify fallback posts summary comment when inline comments fail
## Summary
- Add HTTP response status checking to all Gitea tracker methods that were silently swallowing errors
- Add fallback in create_pr_review: if inline comments fail, retry as plain PR comment
## Test plan
- [ ] Deploy and trigger a PR review, check logs for actual error details
- [ ] Verify fallback posts summary comment when inline comments fail
The Gitea tracker was silently swallowing HTTP error responses — only
network failures were caught, so 4xx/5xx from Gitea went unnoticed and
the agent logged success even when reviews weren't posted.
- Add response status checking to create_pr_review, update_issue_status,
and add_comment
- Add fallback in create_pr_review: if inline comments fail, retry as a
plain PR comment so the summary still gets posted
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Add /health endpoint to the MCP server and probe it from the dashboard
on page load to update server status (running/stopped) in real time.
Co-Authored-By: Claude Opus 4.6 (1M context) <noreply@anthropic.com>
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Summary
Test plan