GitLab projects & issue workflow
Connect an allowed GitLab project and review issue work through the shared execution flow.
WHEN IT HELPS
Put it to work.
Bring a GitLab team into the same task, model and approval system without treating a merge request as an automatic merge.
Before you begin
- Workspace administration permission and a supported GitLab connection.
- An allowed project, authenticated webhook and enabled executor for Issue → MR.
WALK THROUGH IT
See the workflow, step by step.
Synthetic sample content, with simplified screens. No model call, upload, account change or paid task runs here.
Open GitLab, select the workspace and use the provided connection form. Choose only projects that the workspace is allowed to access.
Configure the authenticated webhook as instructed by your administrator. Review received issue commands, source revision and the selected model.
Follow actual phases and approvals. Inspect checks and file changes, then explicitly approve a draft merge request when the workflow reaches publication.
GitLab / Example project connection
THE USEFUL RESULT
What you should leave with.
A project connection and, when enabled and successful, a reviewed draft merge-request workflow.
Know the boundaries.
- The beta connection is token-based; do not assume OAuth or arbitrary self-managed GitLab hosts are supported.
- Automatic review comments and every possible @gonu command are not promised by this guide.
IF SOMETHING DOESN’T WORK
Projects or issue execution are unavailable.
Check token access, workspace role, allowed project, authenticated webhook and the displayed executor status with your administrator.
Contact support