Skip to content
Shipyard
Back to the roadmap

#9 Add a back-to-top link at the bottom of long pages

Live

From request to production in 3 h 29 min. Automation asked a person for help 1 time.

The journey

Every step from GitLab's own records: the issue, its merge request and their label history.

  1. Filed A project member, in GitLab

    Screened and filed as a GitLab issue.

  2. Triage accepted Triage agent ai-shipyard-triage-gitlab-ai-hackathon

    Wrote the acceptance criteria. Record

    · 1 min 3 s later

  3. Build started Dispatcher

    Started the build agent with the criteria.

    · 1 s later

  4. In review Dispatcher

    Every test and scan passed; the review agent started.

    · 6 min 13 s later

  5. Asked a human Dispatcher

    Automation stopped and asked for help.

    · 55 min later

  6. Back to triage Dispatcher

    Restarted from triage.

    · 2 h 11 min later

  7. Triage accepted Triage agent ai-shipyard-triage-gitlab-ai-hackathon

    Wrote the acceptance criteria. Record

    · 54 s later

  8. Build started Dispatcher

    Started the build agent with the criteria.

    · 1 s later

  9. Merge request opened Build agent

    Add a "Back to top" link to the roadmap and changelog Record

    · 2 min 16 s later

  10. In review Dispatcher

    Every test and scan passed; the review agent started.

    · 3 min 22 s later

  11. Approved Review agent ai-shipyard-review-gitlab-ai-hackathon

    Checked against the criteria.

    · 58 s later

  12. Merged Dispatcher

    Merged at the reviewed commit, with a release decision record. Record

    · 4 s later

  13. On staging Pipeline

    Merged, deployed to staging and smoke-tested.

    · 5 min 1 s later

  14. Live Pipeline

    Passed a canary and a 60-second watch in production.

    · 2 min 43 s later

Why it was safe to merge

What the dispatcher verified before merging, from its release decision record (open it).

Issue #9 on GitLab Its merge request