GitLab + Elido: release and MR automation is planned
There is no GitLab integration yet. Release-note shortening and merge request comments are planned. A GitLab CI job can call the Elido REST API today.
Was Sie tun können
Where this stands
How it works
Nothing runs between Elido and GitLab yet
There is no connector, OAuth app or background job for GitLab. Elido does not send anything to GitLab and does not read from it.
Today
What works today
These steps use features that exist now. They do not need an GitLab connection in Elido.
- 1Create an Elido API key
Dashboard, API keys. Store it as a masked GitLab CI/CD variable.
- 2Call the REST API from a CI job
Add a job that creates or updates the short link for your release URL. See the API reference for the links endpoints.
- 3Create a webhook
Dashboard, Webhooks: add an HTTPS endpoint and choose the events, for example link.broken or link.scan_failed.
Authentication
No credentials are stored
Elido stores no GitLab credentials. Keep the Elido API key in a masked GitLab CI/CD variable.
Planned
Planned, not built
- Shortening URLs in release notes automatically.
- Merge request comments for tracked URLs.
- A dashboard card to connect GitLab.
Frequently asked questions
Is the GitLab integration available?+
No. It is planned. There is no connector in the product yet.
What can I do today?+
Send Elido webhooks to your own endpoint or an automation tool, or pull data through the REST API.
Which webhook events exist?+
link.created, link.updated, link.deleted, link.broken, link.expired, link.scan_failed, link.cap_reached and domain.ssl_failed. There is no per-click event.
Connect Elido to GitLab yourself, today
Start free. No card required.