GitLab Integration

Before you start

• Git integrations are available on Team plan workspaces.
• You need workspace permission to manage integrations.
• You must create the repository connection in Ouraboard first, then configure GitLab webhook.
• Owner and repository name must exactly match GitLab project path.

Step 1: Connect repository in Ouraboard

1. Open Workspace Settings → Git.
2. Set provider = GitLab.
3. Fill:
   • Repository owner (for gitlab.com/acme/my-repo it is acme)
   • Repository name (for gitlab.com/acme/my-repo it is my-repo)
   • Webhook secret (or use Generate)
   • Default branch (usually main)
4. Click Connect.
5. In Connected repositories, copy the full Webhook URL using Copy URL.

You do not need to manually build URL or integration ID. Use the value shown in the connected repository row.

Step 2: Create GitLab webhook

1. Open your repository in GitLab.
2. Go to Settings → Webhooks.
3. Paste the Webhook URL copied from Ouraboard.
4. Paste the same Webhook secret into GitLab secret token field.
5. Select:
   • Push events
   • Merge request events
6. Save webhook.

Step 3: Verify end-to-end

1. Create or pick issue in Ouraboard (example slug: PRJ-123).
2. Push commit with slug in message (example: fix: PRJ-123 gitlab test).
3. Optionally create MR with slug in title/description.
4. Open issue → Development tab and verify activity is linked.

Issue linking rule

Include issue slug in commit message or merge request title/description (example: PRJ-123).

Example: fix: PRJ-123 update webhook handling

Recommended commit formats

• fix: PRJ-123 update webhook validation
• feat(PRJ-456): add git activity feed
• chore: cleanup pipeline [PRJ-789]

If no issue slug is present, webhook delivery succeeds but no issue will be linked.

Default branch behavior

• Default branch is used only for optional auto-move branch guard.
• Activity linking from commits/MRs works on any branch if issue slug is present.
• Enable Auto move only when PR/MR targets default branch to avoid moving issues from feature-to-feature merge requests.

Security checks

• Webhook secret is verified for each delivery.
• Unknown projects are rejected.
• Duplicate delivery payloads are deduplicated.

Troubleshooting

• Webhook repository does not match configured integration: verify owner/name in Ouraboard match GitLab project path.
• Request method 'GET' is not supported in webhook test: this is expected for browser GET; GitLab must send POST JSON deliveries.
• Secret mismatch / 401/403: update secret token in GitLab to match Ouraboard.
• No issue linked: include slug like PRJ-123 in commit or MR text.

Screenshot