GitLab merge requests, linked to their cards.
Connect gitlab.com or your own GitLab instance. Commits and merge requests that name a card link themselves to it, merging a request that names the card moves it to done, and production deployments show which commits are live.
Two ways to connect
gitlab.com
Connect with your gitlab.com account through GitLab's own sign-in and pick from the projects where you are a Maintainer or higher. TaskDeck adds the webhook it needs to each one.
Your own GitLab
For self-managed GitLab 15.5 or later, reachable over HTTPS at a public address, use a personal, group or project access token with the api scope and the Maintainer role or higher. TaskDeck shows when the token expires and warns two weeks ahead.
How linking works
- Put the card key in a commit message, or in a merge request's branch name, title or description
- A merge request that names no card links to the cards its commits name
- Opening a merge request links it; merging one that names the card moves the card to the done column
- Deployments to a production environment mark the card's commits live
- Connecting a project also links its earlier commits and merge requests to their cards
- Pick several GitLab projects at once, and connect each TaskDeck project to its own
- A project admin connects GitLab from the project's settings, under Integrations
Sign in to TaskDeck with GitLab and the moves your merge requests on gitlab.com make on the board are credited to you.
GitLab
Questions about the GitLab integration
Does TaskDeck work with self-managed GitLab?
Yes: GitLab 15.5 or later, reachable over HTTPS at a public address, connected with an access token that has the api scope and the Maintainer role or higher.
Which deployments count as live?
Deployments to an environment in GitLab's production tier.
Which plans include GitLab?
Every plan, the Free plan included.
Give your next project a clear starting point.
Create a board, add your first task, and bring your team together.
No credit card required · Free forever plan