GitLab

Code hosting on GitLab.com: projects, issues, merge requests, pipelines and releases.

API keyCopy Anchor Link

1. Open gitlab.com and create an API key with only the access your apps need.
2. Copy it. It may be shown only once.

What to create: A personal, project or group access token from GitLab.com.

Add it to your Gateway. It asks for the key:

everyapp provider add gitlab

Use it in an appCopy Anchor Link

In the app's everyapp.config.ts:

capabilities: {
  gitlab: { access: "read", why: "What the app does with it." },
},

The app calls GitLab's API with integrationFetch(), and the Gateway adds the key. Use "write" if the app changes things. More in API providers.

Check it worked: everyapp provider show gitlab shows the key as set.

Rate limits: 2000 a minute. Authenticated API traffic per user on GitLab.com.

Connect accountsCopy Anchor Link

Each person connects their own GitLab account in the Gateway, once, and every app that asks uses it. Apps never see the tokens. How connecting works

The redirect URI to register, with your Gateway's address (like apps.example.com):

https://<your gateway>/connect/gitlab-oauth/callback

A self-managed GitLab needs a custom provider with its own host in place of gitlab.com.

1. Open gitlab.com and create an OAuth app (also called a client or an integration).
2. Add the redirect URI above.
3. Copy the client ID and client secret. The secret is often shown only once.

Add it to your Gateway. It asks for the client ID and secret:

everyapp provider add gitlab-oauth

Or add it in Manage workspace → Providers.

Use it in an appCopy Anchor Link

capabilities: {
  "gitlab-oauth": { access: "read", scopes: ["api.read"], why: "What the app does with it." },
},

Apps ask for these scope sets:

Check it worked: everyapp provider show gitlab-oauth shows the client as set. Then open the account menu → Connected accounts → Connect GitLab.

Something wrong or missing? Open an issue.