Feedback Modes

Supported public path: GitLab artifact-first

Start with artifact-first delivery, then layer MR feedback on top only after the baseline path is working.

Artifact-first baseline

The public onboarding baseline is the artifact-first workflow:

• The review job writes ai-review.md and ai-review.json.
• Developers inspect the results from the job artifacts first.
• The team validates the review path before adding more delivery noise to merge requests.

This keeps the first successful run narrow, observable, and easy to debug.

Optional MR feedback

MR feedback is a follow-on capability, not the primary onboarding path.

• Use it after the artifact-first workflow is already working for the team.
• Treat MR feedback as an enhancement to the same review run, not a replacement for understanding the artifacts.
• Keep deeper operator, self-hosted, and private-rollout delivery variants outside this public guide.

If MR delivery disappears, is suppressed, or fails after artifact writing, use Troubleshooting instead of switching modes blindly.

How to choose the next step

• Stay on the artifact-first path when you are still proving the workflow or onboarding a new team.
• Move to MR feedback when you want the review result to appear directly in merge request collaboration.
• Return to First review output if you still need to confirm the artifacts before changing delivery mode.
• Use Troubleshooting if feedback delivery and artifact output no longer agree.

Next step: Reference

Also continue with:

• First review output
• Troubleshooting