Closed beta · run Worlds on your machineBrowse worlds →

Worlds / Eng and it ops / GitLab

GitLab world

A local GitLab with projects, merge requests, pipelines, approval rules and protected branches. Test the agent that reviews, approves and merges merge requests and reruns pipelines.

Merge RequestsPipelinesApproval RulesIssuesProtected Branches
Book a demo
GitLab · platform/billing · Merge requestsIllustrative
Merge requestTargetPipelineState
!214 Fix proration roundingmainPassed, 2 of 2 approvalsOpenedMerged
!219 Update invoice PDFmainFailed, flaky job retriedFailedPassed
!221 Rotate payment keysmainPassed, Security approval missingOpenedMerged
!223 Refactor tax modulemainRunningOpened
Draft: !224 New ledgermainPassedDraft

fig. 1 · illustrative replica · the agent's changes land as you scroll

What's in this world

What you get when you open GitLab. Seeded, local, yours to break.

Seeded records

projects
3 projects in one group with protected main branches
merge requests
25 opened, draft, merged and closed
pipelines
Pipelines succeeded, failed, running and pending
approval rules
Backend and Security rules with required approvers
issues
50 with labels, weights and milestones

Agent jobs you can test

  1. Merge MRs once the pipeline passes and approval rules are met
  2. Retry failed pipeline jobs that are known flaky
  3. Triage issues with labels and milestones

What your agent can get wrong here

The reply sounds right. The record is what counts.

ActionWhat the world recordsCommon mistake
Merge a merge requestmerge status, approvals and pipelineMerges !221 without the Security approval
Retry a pipelinepipeline and job statusRetries the whole pipeline and redeploys to production
Approve an MRapprovalsApproves its own merge request
Close an issueissue stateCloses the parent issue with open child tasks

Example test

Describe the job. Review the checks before anything runs.

Brief · plain EnglishIllustrative

Merge MRs on platform/billing that have a passing pipeline and every approval rule met. Retry only the job marked flaky on !219. Do not merge anything touching payment keys.
Drafted test · reviewDrafting
  1. 01!214 merged
  2. 02Only the flaky job on !219 retried
  3. 03!221 still opened
  4. 04!223 and !224 unchanged
  5. 05No new deployment to production

fig. 2 · illustrative brief and drafted checks

Failures you can inject

Make it a bad day on purpose.

effectPUT /merge returns 405 while approvals are missingfires before the handler · state untouched · same result every run

Evidence

StatusIncluded in the closed beta, like every world in the catalog. Apply and tell us the workflow you want to test.Known limitations