GitLab + Elido — release shortening and MR comments on tracked URLs
Auto-shorten release note URLs on every GitLab Release. Get an automatic MR note when a diff touches a URL Elido redirects. Supports GitLab.com and self-managed instances. Personal access token — two steps.
What you can do
Short links in releases, safety net on MRs
How it works
Bidirectional — GitLab events in, Elido notes out
Elido registers a System Hook on each selected GitLab project using your PAT. GitLab pushes release and merge_request events to Elido's webhook-dispatcher. For releases, Elido scans the release body for URLs and creates short links. For MRs, Elido reads the diff for URLs that match tracked Elido links and posts a note via the GitLab Notes API. The PAT is the only credential — no OAuth app registration required.
release.published or merge_request.opened fires to Elido's webhook
Scans release body for URLs or MR diff for tracked links
Short links on release; affected link IDs on MRs
Setup guide
Two steps to release shortening and MR comments
- 1Generate a GitLab Personal Access Token
GitLab → User Settings → Access Tokens → New token with `api` + `read_repository` scopes.
- 2Paste in Elido + pick projects
/dashboard/webhooks → GitLab → paste PAT + select projects to watch.
Authentication
Personal Access Token — scoped, encrypted at rest
The GitLab integration uses a Personal Access Token with the api and read_repository scopes. You generate the token from GitLab → User Settings → Access Tokens and paste it once into Elido. Elido encrypts it with your workspace's KMS key before storage. The key is decrypted in memory only when making API calls and never logged or displayed after the initial paste. You can revoke the token from GitLab at any time, and you can remove the integration from /dashboard/webhooks → GitLab → Remove.
For self-managed GitLab, the PAT should have access only to the projects you select during Elido setup. Avoid using an admin token — a user-scoped PAT with api + read_repository is sufficient.
Frequently asked questions
How is the GitLab integration different from the GitHub integration?+
The functionality is the same — release shortening and MR comments on tracked URLs. The auth model differs: GitLab uses a Personal Access Token you generate, while GitHub uses an OAuth GitHub App install. Both approaches keep Elido's access minimal and revocable.
What GitLab scopes does the PAT need?+
api (for creating notes / comments on releases and MRs) and read_repository (to read release bodies and MR diffs). write_repository is not required — Elido never pushes code.
Does the integration work on self-hosted GitLab?+
Yes, self-managed GitLab instances are supported. During setup, paste your GitLab instance URL (e.g. https://gitlab.example.com) along with the PAT. The webhook endpoint is configured automatically.
What does Elido comment on a merge request?+
When an MR diff contains a URL that Elido is currently redirecting, elido-bot posts a note listing the affected Elido link IDs, destination URL, and current click count. No code changes, no approvals — just a heads-up comment.
How do I revoke Elido's access to GitLab?+
Remove the integration from /dashboard/webhooks → GitLab → Remove. The stored PAT is deleted from Elido. You can also revoke or delete the PAT from GitLab → User Settings → Access Tokens.
Release notes with short links — every release, automatically
Start free. No card required.