GitLab Duo adds agent actions to GitLab projects. Code Review Flow analyzes a merge request and leaves comments on the changes.
Check where the change is discussed
GitLab Duo Agent Platform runs agents and workflows within GitLab. Apply Code Review Flow to a merge request to see findings alongside the diff. Start with one project. Check the permissions, the available runner, and the conditions that trigger the flow. If the agent leaves no comments, check whether the CI job ran before drawing conclusions about the code.
The stream has launch environment requirements. The documentation separately describes the case with its own runner and GitLab hosted runners. Check the conditions for a specific installation by version and type of deployment.
Change settings in CI
A variable has been added to the training merger request, including tests of the new data scheme. In the project audit instructions, specify that this setting should not affect the assembly of the main branch. The file format .gitlab/duo/mr-review-instructions.yaml is described in the help. If the agent has indicated an extra run, open the task rules and check at which launch source the condition is triggered.
Repeat the check for a regular branch and a merge request. Some conditions look identical until the CI variables are evaluated. For a disputed finding, record the configuration that reproduces it.
Rights, Executor and Credit
Agent review is attached to the project and runs in CI/CD. GitLab documents runner requirements and usage accounting for the service account. When configuring the team workflow, check which projects have access to the flow and how often it runs when a merge request is updated repeatedly.
Suitable tasks
- Run a merge request review in GitLab
- Use project rules in agent review
Strengths
- View results are next to the changes
- The documentation separates project, flow, and CI runner settings
Limitations
- Execution depends on the available CI runner and project permissions
- Credit cost and process availability depend on the GitLab configuration
Selection and conditions
- Free access
- Not confirmed
- Trial period
- Not confirmed
- No sign-up required
- Not confirmed
- Russian interface
- Not confirmed
- Local installation
- Not confirmed
- API
- Yes
“Not confirmed” means there is not enough information. The feature may still be available; check the developer’s terms.
- Input formats
- Code, Text
- Result
- Code, Text
Terms
GitLab and GitLab Credits subscription terms apply. The availability of individual processes is indicated in the certificate. Credit cost and process availability depend on the GitLab configurationFrom task to first result
Practical example
- Task
- Run a merge request review in GitLab
- What to prepare
- An example merge request with a CI change and a rule for running the new schema tests.
Task brief or prompt
Training task: add the test run rule for the desired branch to the instructions. Request a change check of the CI and review comments on startup types and variables.
Expected result
A comment in the merge request that states the condition and how to test it.
How to check the result
- Check the status of the CI task before reading the results.
- Play the condition on the desired startup type.
An editorial teaching example of a task brief, not the result of hands-on testing of the service. Check that the required mode is available, that you have rights to the source material and that the intended use of the result is permitted.
Check details
Official sources
- GitLab Duo
- Code Review Flow Requirements and Launch Configuration
- GitLab Duo Workflow API
- Terms of access and payment
- Configure instructions for Code Review Flow
This description is based on the developer’s material. Features, prices and availability may change; check the primary source before use.