dusk bot
routinesgitlab merge request digest

dusk botroutines

see what is holding up open gitlab merge requests

go into the release meeting knowing which merge request needs a fix and which needs an answer. this digest reads the pipelines and discussions on open gitlab merge requests aimed at one branch.

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

it brings the evidence to chat. a failed pipeline and an unresolved thread each get their own line, even on the same change.

pixel art: an indigo pixel bot and a blue pixel bot beside a tile saying GitLab, a magnifying glass and a newspaper, on a grassy meadow in front of snowy hills and green fields, one saying "one thread still open"

the message

paste this into a chat with your bot

every weekday at 11 am, list all open, non-draft merge requests targeting the branch "release" in my gitlab project brookmill/print.

read each request’s latest commit and its pipelines and discussions. use the newest pipeline for that commit. list a failed pipeline, unresolved review thread or missing current pipeline in this chat. include the project, request number, title and the evidence. group by request. don't treat a running pipeline as failed.

never merge, approve, retry a pipeline or resolve a thread. stay quiet if all reads succeed and none of those conditions apply. if discussions or pipelines are inaccessible, name the request and the missing source.
when
weekdays at 11 am, looking at the current state of one target branch
needs
gitlab read access for project merge requests, commits, pipelines and discussions3. swap in your project path and target branch.

what comes back

an example, not a real run

brookmill/print · release branch
!36 · keep trim marks inside the proof
- pipeline 582 failed on current commit 8b62f11.
- unresolved: erin walsh asks whether the left margin includes the binding allowance.
!41 · revise stock labels
- no pipeline found for current commit 72bc830.

make it yours

  • use the branch you actually release. give its exact name if it changes each milestone.
  • focus a meeting on discussion. request only the unresolved questions if another person already handles failed builds.
  • keep long threads readable. quote the open question briefly and include its thread reference when available.

when it goes wrong

  • an old failure follows a new commit. match the pipeline to the latest commit before giving its status. if none matches, say so.
  • a lively conversation looks unresolved. count review threads that carry an unresolved status. a long exchange can simply mean two people talked through a decision.

keep pipeline status and human feedback separate

a passing pipeline cannot answer a reviewer’s question about a margin. give the release lead enough detail to open the right discussion. a missing pipeline also deserves its own wording. no result gives you no evidence of failure.

if the decision is whether to merge right now, open gitlab and inspect the current request. the 11 am digest describes what the bot saw then.

questions

does a clean digest mean every request can merge?

silence has a narrower meaning. the bot found none of the conditions you asked it to list. approvals and other merge requirements sit outside this routine.

why leave drafts out of the release meeting?

their authors may still be writing the change. if an upcoming draft matters, ask for it under a separate heading so it keeps its draft status.

sources

  1. dusk bot docs: routines
  2. dusk bot docs: files and apps
  3. composio: gitlab actions, 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].