Skip to content

GitHub Pull Request Reviews

Agentic Unit can review pull requests in repositories that were approved during onboarding. To request a review, add a new pull request comment containing the mention configured for your environment.

Environment Default mention
Development @ACA-DEV
Integration @ACA-INT
Consolidation @ACA-CONS
Production @ACA-PROD

The platform team can override these values. If a mention does not work, check the value configured for your environment instead of trying mentions from another environment.

For example, in Development:

@ACA-DEV please review this pull request. Focus on error handling and test coverage.

The mention is case-insensitive. The rest of the comment becomes the review request, so include any areas of focus, constraints, or checks that would help the agent.

Before You Begin

Confirm that:

  • Your team has completed onboarding.
  • The platform GitHub App is installed for the GitHub organisation and can access the repository.
  • The repository is linked to your Agentic Unit team.
  • Branch protection prevents important branches from being deleted and requires a pull request and approval before changes can be merged.
  • The pull request is ready for review.

What Starts A Review

A review starts only when all of these conditions are met:

  • A user creates a new comment on a pull request.
  • The comment contains the configured mention.
  • The author is not a bot.
  • The GitHub App can access the repository.

Mentions in regular GitHub issues do not start a review. Editing an existing comment to add the mention does not start one either; add a new comment.

Any qualifying comment can trigger a review, including one that quotes an old mention. Use the mention only when you intend to start Agentic Unit.

What Happens Next

Agentic Unit adds a commit status named ACA / PR Agent while the review is running and updates it when the job finishes. Where available, its details link opens the job chat.

The agent inspects the pull request and posts its complete review as one comment in the pull request conversation. It does not add comments to individual code lines, change the pull request, approve it, or merge it.

Treat the review as an additional input. Developers remain responsible for checking the findings, reviewing the code, and deciding whether the pull request should be merged.

If A Review Does Not Start

Check the following:

  1. The mention matches the current environment.
  2. The comment is new and is attached to a pull request, not an issue.
  3. The comment was posted by a person, not a bot.
  4. The GitHub App installation includes the repository.
  5. The repository is linked to your Agentic Unit team.

If it still does not start, contact your Agentic Unit platform team with the environment, pull request URL, comment URL, and approximate trigger time. Do not include credentials or secrets.