Git Integrations

Connect your repositories to your project board

Link commits, branches, and pull requests from GitHub, GitLab, Bitbucket, or Gitea directly to your tickets. See git activity on every ticket and auto-move tickets through your workflow.

Get started free
Commit tracking

Every commit that references a ticket shows up in its Git Activity section with a direct link.

Pull request linking

PRs and merge requests are linked to tickets - see their status, author, and whether they have been merged.

Auto-move tickets

Automatically move tickets to In Progress, Review, or Done based on commit and PR events.

Signature verification

Every webhook is verified using HMAC signatures (GitHub, Bitbucket, Gitea) or secret tokens (GitLab).

How it works

From commit to ticket in seconds

Reference a ticket in your commit message, branch name, or PR title - Todo4you does the rest.

1

Add a webhook

Create a GitHub, GitLab, Bitbucket, or Gitea integration in your project settings. Copy the webhook URL and secret into your repository.

2

Reference tickets

Include your ticket reference in a commit message, branch name, or PR title - e.g. PRJ-42 or #42.

3

Events appear on tickets

Commits, branches, and PRs show up in a dedicated Git Activity section on the ticket detail page with direct links back to your repository.

4

Tickets move automatically

Configure auto-move rules to advance tickets through your workflow when commits are pushed or PRs are opened or merged.

Supported providers

Works with the platforms you already use

All four providers share the same feature set - pick the one your team uses, or connect multiple repositories at once.

GitHub

Receive push and pull request events from any GitHub repository via webhooks.

Setup in GitHub

1

Create the integration in Todo4you under Project Settings - Integrations - GitHub. Save to generate your webhook URL and secret.

2

In your GitHub repository, go to Settings - Webhooks - Add webhook.

3

Paste the Webhook URL, set Content type to application/json, and paste the Secret.

4

Select "Let me select individual events" and enable Pushes and Pull requests.

Security: GitHub signs each payload with HMAC-SHA256 using your secret. Todo4you verifies the X-Hub-Signature-256 header on every request.

Supported events

Todo4you processes these GitHub events and extracts ticket references from commit messages, branch names, PR titles, and PR descriptions:

Push events
Each commit in a push is stored individually with SHA, message, author, and a link back to the commit on GitHub.
Pull request events
Opened, closed, and merged events are tracked with PR title, number, author, and a link to the PR on GitHub.
Branch events
Branch creation and deletion are tracked when the branch name contains a ticket reference.

GitLab

Receive push and merge request events from any GitLab project - cloud or self-hosted.

Setup in GitLab

1

Create the integration in Todo4you under Project Settings - Integrations - GitLab. Save to generate your webhook URL and secret token.

2

In your GitLab project, go to Settings - Webhooks.

3

Paste the Webhook URL and the Secret Token.

4

Enable Push events and Merge request events as triggers.

Security: GitLab sends your secret in the X-Gitlab-Token header. Todo4you verifies it matches on every request.

Works with self-hosted GitLab

The integration works with both GitLab.com and self-hosted GitLab instances. As long as your GitLab server can reach your Todo4you webhook URL, everything works the same way.

Push Hook
Commits in a push are stored with SHA, message, author, and a link to the commit.
Merge Request Hook
Opened, closed, and merged events are tracked with MR title, number, author, and a direct link.

Gitea

Receive push and pull request events from your self-hosted Gitea instance.

Setup in Gitea

1

Create the integration in Todo4you under Project Settings - Integrations - Gitea. Save to generate your webhook URL and secret.

2

In your Gitea repository, go to Settings - Webhooks - Add Webhook - Gitea.

3

Paste the Webhook URL, set Content type to application/json, and paste the Secret.

4

Select "Choose events" and enable Push and Pull Request.

Security: Gitea signs each payload with HMAC-SHA256 using your secret. Todo4you verifies the X-Gitea-Signature header on every request.

Perfect for self-hosted teams

If your team runs its own Gitea server, this integration lets you connect your private repositories to Todo4you without giving access to any third party. All communication happens via standard webhooks.

Your server, your data
Todo4you only receives the events your Gitea server sends - we never connect to your Gitea instance directly.
Same features as GitHub/GitLab
Commit tracking, PR linking, branch events, and auto-move all work identically across providers.

Bitbucket

Receive push and pull request events from any Bitbucket Cloud repository via webhooks.

Setup in Bitbucket

1

Create the integration in Todo4you under Project Settings - Integrations - Bitbucket. Save to generate your webhook URL and secret.

2

In your Bitbucket repository, go to Repository settings - Webhooks - Add webhook.

3

Paste the Webhook URL and the Secret.

4

Select Repository push and Pull request triggers (Created, Updated, Merged, Declined).

Security: Bitbucket signs each payload with HMAC-SHA256 using your secret. Todo4you verifies the X-Hub-Signature header on every request.

Supported events

Todo4you processes these Bitbucket events and extracts ticket references from commit messages, branch names, PR titles, and PR descriptions:

Repository push
Each commit in a push is stored individually with hash, message, author, and a link back to the commit on Bitbucket.
Pull request events
Created, updated, merged (fulfilled), and declined events are tracked with PR title, number, author, and a link to the PR on Bitbucket.
Branch events
Branch creation and deletion are tracked when the branch name contains a ticket reference.
Auto-move

Let your git workflow drive your board

Configure rules per integration to automatically advance tickets through your workflow. Tickets only move forward, never backwards.

On first commit

When the first commit referencing a ticket is pushed, automatically move it to a status of your choice - for example, In Progress.

Backlog to In Progress

On PR opened

When a pull request or merge request is opened, move the ticket to Review or any other status you configure.

In Progress to Review

On PR merged

When a pull request or merge request is merged, move the ticket to Done. Your board stays in sync with your codebase.

Review to Done
Ticket detail

See git activity right on the ticket

Every linked commit, branch, and pull request appears in a dedicated section on the ticket detail page - with direct links back to your repository.

PRJ-42 Fix authentication redirect on mobile
Git Activity
Fix auth redirect for mobile browsers merged
octocat - 2h ago
Fix auth redirect for mobile browsers opened
octocat - 5h ago
a3f8c21 Handle mobile Safari redirect edge case
octocat - 6h ago
e7b4d09 PRJ-42: Fix OAuth callback for mobile
octocat - 1d ago
fix/PRJ-42-auth-redirect created
octocat - 1d ago

Connect your first repository today

Create a free account, set up your board, and link your GitHub, GitLab, Bitbucket, or Gitea repository in minutes.

Get started free

Coming soon

Our native apps for iOS, macOS and Android are in development and will be available on the App Store and Google Play soon.