dusk bot
integrationsgitlab

dusk botintegrations

which gitlab merge request needs a reviewer?

find the thread holding up a merge before you ask someone to review it again. a gitlab bot in dusk can read open merge requests, their discussions and the jobs behind a failed pipeline.

by the dusk bot team · checked · how we made this

give it a project and target branch. ask for the request number and the next decision in your chat.

pixel art: a cyan pixel bot, an orange pixel bot and a blue pixel bot beside a tile saying GitLab and a signpost, on a sandy path in front of a lily pond, one saying "which review is stuck"

what a bot can do in GitLab

start at the merge request and follow the evidence. a reviewer can answer a design question. a failed test needs someone to read the trace. these actions help you tell which job comes next.

actiondusk bot treats it aswhat you would use it for
Get Project Merge Requestsreadfind open requests aimed at the release branch
List Merge Request Discussionsreadread the follow-up under a reviewer’s original question
List Merge Request Dependenciesreadfind another request that must land first
Get Merge Request Approvalsreadsee who has already approved the change
List Project Pipelinesreadfind failed pipelines for the branch under review
List Pipeline Jobsreadpick out the failed job within a pipeline
Get Job Tracereadread the failing command and its error

composio, the connection service behind dusk bot's apps, lists 317 GitLab actions (version 20261116_00, read 20 november 20264). dusk bot treats 158 as reads, 9 as sends and 150 as changes.

only actions starting with a read word (get, list, search) count as reads, so a read-only bot can't call the rest. a send reaches people or moves money, like create commit comment, and waits for your Allow unless you set a daily amount.

connect GitLab

  1. open Connected apps in the sidebar.
  2. pick GitLab and sign in on GitLab's own page, so your password goes to them and never to a bot.
  3. choose which bots may use it, and whether each may only read or may also change things. your bookkeeper doesn't need your GitLab.
  4. ask in plain words. reading and drafting happen freely; sending asks you first.

give the review bot a project it can read. sign in to gitlab from connected apps. choose the bot, grant reading access and tell it the target branch. try one open request by number before asking it to cover the whole branch.

routines to copy

pick the question your release meeting keeps circling back to. each message leaves the answer in dusk chat. none needs permission to approve code or retry a job.

questions left in review

every weekday at 10, read open merge requests targeting our release branch. find reviewer questions with no answer later in the discussion. give me the request number and the question here. skip drafts and resolved threads.

weekdays at 10 · a reading list for the next review session

first error in the job

at 3 each weekday, find the latest failed pipeline on our default branch. open the failed jobs and read their traces. list the job names and the first relevant error for each here. leave out environment values. never retry a job.

weekdays at 3 pm · job ids and errors to investigate

merge order

every thursday at noon, list the open requests targeting our release branch. follow their recorded dependencies. show which request needs to land before which other one. flag any dependency you cannot see. leave the merge buttons to me.

thursdays at noon · a proposed merge order with any missing dependencies

what it asks you first

leave approval, merge and retry off the action list. these actions change gitlab and can run without a send prompt. keep reviews read only. if you enable a change later, write “ask me before you change anything” into that routine. replying to a discussion counts as a send and asks first by default.

careful with Full access: a bot there with no sending rule can send up to 25 a day without asking. give it Ask every time.

what it cannot do

  • see a private blocker through its dependent request. gitlab omits the blocking request details when your account lacks access.
  • tell which approval rule passed from the approver list alone. rule-level approval state needs gitlab premium or ultimate.
  • start on a gitlab event through this connector. use a schedule for review rounds.

when to stay in gitlab

keep merge decisions with the people who own the branch. if you only need to approve one change, open its diff in gitlab. use the bot when the answer spans several discussions or a pipeline trace you would otherwise have to track down.

what it looks like

a fictional example.

before

martin cole opens a release request with an approval and a failing pipeline. the reviewer already answered the design question.

after the bot

next stop: the package job. the trace says the manifest is missing. no further review request yet.

an illustration with made-up names and numbers.

questions

can i read reviews across a whole release branch?

yes. name the project and target branch. ask the bot to follow every results page before it reports an empty queue.

does a failed job trace explain the cause?

it gives you the error the job printed. ask the bot to quote that line and label any proposed cause as a guess.

sources

  1. dusk bot docs: files and apps
  2. dusk bot docs: routines
  3. dusk bot docs: sending permissions
  4. composio, GitLab toolkit (catalog version 20261116_00), checked 20 november 2026

drafted with ai help from the dusk bot docs and the sources listed on this page, then checked against them. if something here is wrong or out of date, write to [email protected].