Reviews and results

Submit a review

Open Content > Reviews, then select Add review. The collection is at /ai_code_review_ui/review, and the add form is at /ai_code_review_ui/review/add.

Viewing reviews requires view ai_code_review_ui review. Submitting a job requires add ai_code_review_ui review. View permission allows access to reviews across this Drupal site.

Enter a merge request URL, or supply the repository URL, branch, and base and head commit IDs. Choose a registered provider profile and a review policy, or use their configured defaults.

The UI sends repository metadata to the server, requests asynchronous processing, and saves the accepted job as a local review record. It does not compute the review diff itself.

Check status

The review status page offers Check review status; a saved review also offers Refresh status. A status check never submits another review. Cron checks up to 10 pending reviews per run and rotates through them so unchanged or failed checks do not prevent later reviews from being checked.

When the server completes a job, the UI retrieves, validates, and stores its result. A completed server status without a valid stored result remains eligible for polling. Failed, cancelled, and expired jobs retain their status and display a translated message. A missing job (404) or expired job/result (410) becomes expired. Communication and invalid-response failures keep the job pending for a later check.

Do not repeatedly submit a review while waiting. Check its status and retrieve the result after completion. The ordinary review form works without an AI assistant or separate polling scheduler on the UI site.

Read completed reports

Reports use the server's Summary, File/Method, and Detail layout in a dark terminal panel. Feedback wraps, while corrected code and suggestion diffs scroll horizontally and preserve indentation.

With highlight.php configured, PHP, Python, and unified diffs receive syntax highlighting. Other languages use a plain code fallback. Previously saved plain text remains readable, and AI tools return the plain report text.

Saved review request fields are read-only. The former Edit route displays the original request with View review, Check review status, and Create new review links. Saving an existing review never changes or resubmits the job. Create a new review to request a new job.

Handle errors and cancellation

After an uncertain submission error, check the server for an existing job before submitting again. The client does not automatically retry submissions; a fresh submission can create another job. Existing jobs stay bound to their original server URL.

Authentication or permission failures require an administrator to check the service-token Key and Server privileges. Correct invalid input before resubmitting. Replace revoked or foreign provider profiles with an active profile owned by the service account.

For a queued or running review, select Cancel review on its detail or status page, then confirm. This action requires a signed-in account with both view ai_code_review_ui review and edit ai_code_review_ui review access. View-only accounts can still check status. Opening the confirmation page or selecting Keep review does not cancel the job.

The UI requests cancellation from the original review server. If completion wins the race, it shows the actual status instead of claiming cancellation. Work already in progress may take time to stop. Cancelling retains the local review and any saved result; deleting a local review does not cancel a remote job. If cancellation cannot be confirmed, refresh status before trying again. The UI does not automatically retry an uncertain cancellation.