GitLab
Read and create issues in your GitLab projects from your app.
Connecting
Create a personal access token with the api scope in GitLab under your avatar > Edit profile > Access > Personal access tokens, and paste it as-is.
Read project issues
- project_id: The numeric project ID, or the full path like my-group/my-project. Required.
- state: Which issues to read; unset reads all.
- labels: Comma-separated label names to filter by.
- per_page: How many issues per page, up to 100.
- page: Which page of results to read.
Answers with: iid, id, title, state, author, web_url, created_at.
Create an issue
- project_id: The project the issue lands in, numeric ID or full path. Required.
- title: The one-line title of the issue. Required.
- description: The issue details, markdown welcome.
- labels: Comma-separated label names to put on the issue.
- confidential: Hide the issue from users without project access.
- issue_type: What kind of issue this is; unset means a plain issue.
Answers with: iid, id, title, state, author, web_url, created_at.
Triggers
- Issue opened or changed: arrives the moment it happens.
- Comment posted: arrives the moment it happens.
- Merge request opened or changed: arrives the moment it happens.
- Code pushed: arrives the moment it happens.
- Pipeline status changed: arrives the moment it happens.
- Release created or updated: arrives the moment it happens.
Settings
- Project: The project issues read from and land in when the call names none, numeric ID or full path.
- Issue title: The issue title with field slots, or bind an input on screen.
- Issue details: The issue description with field slots, markdown welcome.
What it stores
Issues (iid, id, title, state, author, labels, web-url, created-at, project-id)
Where it speaks
This connection reaches https://gitlab.com and nowhere else. The hosts are fixed by declaration.