fix(pr-reviewer): resolve PR author from sender login

Merged
KH
5mo ago
+146-66

User description

Restore pr-reviewer firing for allowlisted PR authors by falling back to sender.login when pull_request.user.login has not materialized yet. This keeps the REVIEW_AUTHORS gate fail-closed for resolved authors, marks unresolved skips as notify-worthy, and leaves the Slack-notify policy change for a separate PR.

Summary by cubic

Fixes PR author resolution in the reviewer agent by falling back to sender.login when pull_request.user.login is missing, ensuring allowlisted authors still trigger reviews. Unresolved-author skips now set notify: true to flag attention.

  • Bug Fixes
    • Use payload.sender.login as a fallback author for PR-shaped events.
    • When REVIEW_AUTHORS is set and author is unresolved, return a skip with notify: true.
    • Added tests for fallback author and unresolved-author skip behavior.

CodeAnt-AI Description

Resolve PR author from the webhook sender when opener info is missing

What Changed

  • PR review now uses the webhook sender as the author when the pull request opener login is not available, so allowlisted authors still receive reviews
  • When the author cannot be resolved, the skip now marks the PR for follow-up instead of silently skipping it
  • Added tests for the sender fallback and the unresolved-author skip behavior

Impact

✅ Fewer missed reviews for allowed authors
✅ Clearer follow-up on unresolved PR authors
✅ More reliable PR review routing

💡 Usage Guide

Checking Your Pull Request

Every time you make a pull request, our system automatically looks through it. We check for security issues, mistakes in how you're setting up your infrastructure, and common code problems. We do this to make sure your changes are solid and won't cause any trouble later.

Talking to CodeAnt AI

Got a question or need a hand with something in your pull request? You can easily get in touch with CodeAnt AI right here. Just type the following in a comment on your pull request, and replace "Your question here" with whatever you want to ask:

@codeant-ai ask: Your question here

This lets you have a chat with CodeAnt AI about your pull request, making it easier to understand and improve your code.

Example

@codeant-ai ask: Can you suggest a safer alternative to storing this secret?

Preserve Org Learnings with CodeAnt

You can record team preferences so CodeAnt AI applies them in future reviews. Reply directly to the specific CodeAnt AI suggestion (in the same thread) and replace "Your feedback here" with your input:

@codeant-ai: Your feedback here

This helps CodeAnt AI learn and adapt to your team's coding style and standards.

Example

@codeant-ai: Do not flag unused imports.

Retrigger review

Ask CodeAnt AI to review the PR again, by typing:

@codeant-ai: review

Check Your Repository Health

To analyze the health of your code repository, visit our dashboard at https://app.codeant.ai. This tool helps you identify potential issues and areas for improvement in your codebase, ensuring your repository maintains high standards of code health.