GitLab

Issues over OAuth, with labels as the board — on gitlab.com or your own instance.

GitLab connects over OAuth: Connect GitLab — to gitlab.com, or to your own instance when the server is configured for it. One connection per organization.

• What you connect: a GitLab project. Open issues sync in; closed ones do not.
• Labels are the statuses. GitLab issues are natively just open or closed, so the community convention applies: your status labels form the board, plus a synthetic Open status for unlabelled issues. An outbound status change removes the old status label and adds the new one, leaving other labels untouched.
• Closing an issue retires its task. Since only open issues sync, the panel shows work in progress, never an archive. This is GitLab-specific and worth knowing before you wonder where a task went.
• Sync is by poll, about every 30 seconds. Published artifacts upload inline into issue notes.

GitLab also feeds repository triggers. When you connect it, Peractor provisions webhooks for pushes, tags, and merge requests — merge requests speaking the same pull_request.* vocabulary as GitHub's.

Runs pushing branches and opening merge requests use a git credential from Settings → Git access, which works for gitlab.com and self-managed instances alike.