Kodavara Guide

GitHub, GitLab and ClickUp: Let Pull Requests Move the Task

GitHub, GitLab and Bitbucket are all native ClickUp integrations. They link commits, branches and pull requests to tasks by task ID, and a status can be set from the commit or PR text. GitHub also has ClickUp automation triggers for PR events. This guide covers the conventions that make it work and the configuration we build for developer workflows.

Last reviewed October 2026. ClickUp changes often, so check ClickUp's help center for the latest. Written by Kodavara, an independent ClickUp Partner. Not published or endorsed by ClickUp.

What ClickUp Does Today

What You Can Do Natively

Start with the features available on your ClickUp plan.

Task ID Linking

Include the ClickUp task ID in a branch name, commit message or PR title and the work links to the task.

Status From Text

A syntax in the form task ID plus a status in brackets can change the task status from a commit or PR.

GitHub Automations

ClickUp automations can trigger on GitHub events such as a PR state change, a review state change or a new PR branch.

GitLab and Bitbucket

Both link by task ID and can create branches or merge requests. Automation triggers may differ from GitHub, so verify before relying on them.

Where It Falls Short

The Gaps People Run Into

If these are your problem, keep reading.

Linking depends on people remembering the ID convention, so a branch without it is invisible to ClickUp.
The status text syntax must match your statuses exactly or nothing changes.
Automation triggers differ across the three tools, and plan limits on automation runs may apply.
Self-hosted GitHub Enterprise or GitLab setups need their own testing.
Feature requests on ClickUp feedback ask for better linking, which suggests manual steps remain.

Worked Example

Example: Branch to Done

A typical flow. Statuses are illustrative.

Developer Action	Task Result	Mechanism
Create branch with task ID	Branch appears on the task	ID in branch name
Open pull request	Status moves to Code Review	GitHub automation
Reviewer approves	Status moves to Ready to Merge	Review state trigger
Merge	Status moves to Done or Deployed	PR state trigger
Hotfix commit with status text	Status set directly	ID and status syntax

Sample data for illustration.

The Configuration

The Configuration: What We Build and Monitor

Built around your branching and review process.

Part	What We Build	What We Watch
Conventions	Branch, commit and PR naming rules that include the task ID	Work without IDs
Statuses	Dev statuses that match the text syntax and the automations	Renamed statuses breaking links
Automations	PR opened, approved and merged triggers that move tasks	Automation run limits
Templates	PR templates and commit hooks that remind developers of the ID	Skipped checks
Release Reporting	A dashboard of tasks by status and merged work	Tasks stuck in review
Custom Flows	GitHub Actions or webhooks calling the ClickUp API where native triggers fall short	Failed webhook calls