resolved
GitLab
gitlab.com/{group}/{project}
landed in 38msBookSlash for GitLab · Engineering
b/repo.
b/mrs. b/pipelines.
GitLab packs Git hosting, CI/CD, issue tracking, and security scanning into one platform — and one set of buried URLs. BookSlash gives every important view a memorable shortcut your whole team uses.
repo
other shortcuts you might save
b/repob/mrsb/pipelinesb/issues
Suggested slug patterns
Steal these. They work for most teams.
Battle-tested shortcut conventions for GitLab, with notes on why each one survives the URL changes that break personal bookmarks.
- b/repo
Primary GitLab repository.
New engineers learn it day one; survives org migrations.
https://gitlab.com/{group}/{project} - b/mrs
Open merge requests in the team project.
Replaces a fragile bookmark to a saved MR filter.
https://gitlab.com/{group}/{project}/-/merge_requests - b/pipelines
CI/CD pipeline runs.
Engineers check it after every push; saving the URL skips the navigation.
https://gitlab.com/{group}/{project}/-/pipelines - b/issues
Open issues / bug board.
QA, on-call, and engineering managers all reach this URL.
https://gitlab.com/{group}/{project}/-/issues - b/registry
Container or package registry.
DevOps and platform engineers reach it during deploy debugging.
https://gitlab.com/{group}/{project}/-/container_registry - b/security
Security dashboard.
Security and engineering managers review weekly.
https://gitlab.com/{group}/{project}/-/security/dashboard
Common workflows
Three patterns that pay back in week one.
01
Merge-request review
Every engineer types b/mrs on standup mornings. The slug carries the team to the same view; new engineers learn it day one.
02
Pipeline debugging
When CI fails, engineers reach b/pipelines to inspect runs. Pairs with b/registry for the produced artifacts.
03
Quarterly security review
Security leads and engineering managers reach b/security weekly. The slug carries through GitLab UI updates; the same URL works across versions.
With and without
Same GitLab. Different team experience.
Without shortcuts
Each engineer keeps private bookmarks. New hires take a week to memorise which sidebar items matter. Security reviews start with "where’s the dashboard URL?"
With BookSlash
b/repo, b/mrs, b/pipelines, b/issues, b/registry, b/security. Six slugs cover the GitLab surface for engineering and security.
Frequently asked
BookSlash + GitLab
Yes. Slugs are URL → URL; any GitLab URL works including self-hosted instances. The destination still requires GitLab auth.
Same b/ pattern, different destination. Many teams use both: b/repo (GitHub) for one project, b/repo-ci (GitLab) for another. Or namespace by tool: b/gh-repo vs b/gl-repo.
No — slugs route URLs only. Triggering pipelines is GitLab’s job (or your CI tooling’s). BookSlash gets you to the right view in one keystroke.
GitLab Duo lives at URLs you can save as slugs. b/duo for the team Duo dashboard; b/duo-chat for the chat surface. The pattern carries.
Start with one team. Roll out when it sticks.
Your stack. Your shortcuts.
One keystroke for everyone.
2,400+ teams reach every important destination in their stack with a single keystroke. Save the first slug in 30 seconds.
Free for personal use · No credit card · 14-day team trial