How-to
ClickUp GitHub Integration: Link Commits and Pull Requests
How to connect GitHub to ClickUp, link commits and pull requests with a task ID, and which actions need a Workspace connection or Business.
By AIStackMatch Editorial · Updated · 7 min read
Some links on AIStackMatch are affiliate links. We may earn a commission if you purchase or sign up through them, at no additional cost to you. Read our affiliate disclosure.
Short answer
The ClickUp GitHub integration is on every plan. A repository admin adds the repo, then a Workspace owner or admin links it to one or more Spaces. Put a task ID in the branch name, commit message, or pull request and ClickUp attaches the activity. GitHub Automations, which can change a task when a pull request merges, start on Business.
The ClickUp GitHub integration ties a task to the branch, commit, and pull request that implement it. You search files from ClickUp, create a branch or pull request from the task, and read review status without opening GitHub for every update. The code stays in GitHub. Help says attaching a repository does not give ClickUp users access to the codebase.
The integration is on every plan. Automations that fire when GitHub does something, such as a merged pull request, are not. Those start on Business. Sprint setup around this link is in ClickUp for software teams. Other App Center connections are in ClickUp integrations. The index of ClickUp pages is the ClickUp hub.
What does the ClickUp GitHub integration connect?
Two connection types do different jobs. You can use both.
| Connection | Who creates it | What it is for |
|---|---|---|
| Personal | Members and above, for their own GitHub account | Link previews, create issues, branches, and pull requests, and use the GitHub panel on a task. Commands only show what that person can already see in GitHub. The GitHub data is not shared with other people through ClickUp |
| Workspace | Owners and admins. More than one Workspace connection is allowed | Sync activity onto tasks after repos are linked to Spaces, update task status from GitHub, and Workspace Connected Search |
Guests and limited members cannot use the integration. Only a repository admin can add a GitHub repository to ClickUp. After that, a Workspace admin can attach it to Spaces. Only owners and admins change Workspace settings in the App Center, add repos, link them to Spaces, and create the Workspace connection.
A personal connection is enough for one developer who wants to open a branch from a task. A Workspace connection is what makes the team's commits show up on the task automatically.
How do you connect a repository to a Space?
Help splits the Workspace setup into three steps.
- Connect GitHub. Workspace avatar, Apps, GitHub, Workspace tab, Connect. Authorize, choose which repositories Connected Search may use, Save, then Done. You can turn Workspace Connected Search off with the toggle on that tab.
- Add repositories. From the GitHub page in the App Center, Settings, Add repo, and select the repository. Repeat for each repo. Only the connection owner can add repositories. If the list is wrong, you are in the wrong GitHub account.
- Link each repo to one or more Spaces. Settings, click the repo, + Add Space, and select the Space. A Space can hold several repositories. A repository can be linked to several Spaces.
Tasks outside a linked Space will not pick up that repo's activity. Put engineering work in the Space you actually connected. Product specs can stay next to it. The hierarchy for that choice is Spaces, Folders, and Lists.
Branch names created from ClickUp follow a format you can edit under Settings, Auto-generated branch name. The default is :taskId:_:taskName:_:username:. Help's example is CU-ae27de_Auto-generated-naming_John-smith. Spaces in the user name and the task name become dashes. The task ID value includes the required prefix. Save after you change the pattern so the next branch matches the team's convention.
Help's search section says Workspace Connected Search lets members search public files from the repositories you add. You add and remove those repos from the Workspace tab. A Super Agent can search the connected account only after External Search for GitHub is turned on in that agent's profile.
How do you link a commit or pull request?
ClickUp attaches new GitHub activity when a valid task ID appears anywhere in the pull request title, the pull request description, the branch name, or the commit message.
| Form | Example |
|---|---|
#{task_id} | #1abc2de |
CU-{task_id} | CU-1abc2de |
{custom_task_id} | eng-123 |
#{custom_task_id} | #eng-123 |
Ordinary task IDs exist on every plan. You copy one from the task (the ID above the title, or Copy ID in the task menu) or add a Task ID column in List view. Custom task IDs, the prefixed kind such as eng-123, are a Business feature. They are not the same thing as custom task types, which label a task as a bug, an invoice, or a milestone.
When the ID is in a pull request, GitHub gets a comment that links back to the ClickUp task. That comment is posted by the GitHub account of the person who set up the repo and Space mapping. Pasting a pull request link onto a task by hand does not post that GitHub comment.
Hand linking, when the ID was missing: open the task, click the GitHub icon, Add GitHub link, paste, Add. The task has to live in a Space linked to the repo.
To create the GitHub object from the task, you need a personal connection and a linked Space. Open the GitHub icon. The panel offers branch names and commit messages you can copy, and the task ID. Add GitHub link, then New GitHub Issue, New GitHub Branch, or New GitHub Pull Request. Name it, pick the repository, fill in source and target branches when the form asks, and Create.
To set the ClickUp status from GitHub, add the status in square brackets with no space after the ID: #ud5b[ready], or the same pattern with CU- or a custom task ID. Help says this works when you link a commit, push a commit, or create a pull request. The same status change can be an Automation instead.
What do you see on the ClickUp task?
The GitHub icon on a task in a linked Space lists every linked issue, branch, pull request, and commit. The ellipsis copies the link or removes the item. Activity also lands in the task Activity feed. Similar items collapse. Show more reveals them. When a branch is merged, its commits show as one activity item, and you can open the list or jump to a single commit in GitHub. Filter the feed by Git items if the rest of the history is in the way. If something never arrived, the task ID in GitHub is the first thing to check.
| Linked item | Details Help says you can see |
|---|---|
| Issue | Author, reviewers, who created the link, repository, issue status, URL |
| Branch | Author, who created the link, repository, URL |
| Pull request | Author, reviewers, assignees, line changes, who created the link, repository, source branch, target branch, pull request status, URL |
| Commit | Author, changed files, line changes, who created the link, repository, URL |
Add a Pull Requests column on List view or Table view when you want the review state without opening each task. GitHub activity on the task uses the person's ClickUp username, or their GitHub username if they have no ClickUp account.
Pasted GitHub links preview inside the text. A link in the middle of a sentence stays inline, and you can hover it. A link on its own line can be inline, a live preview, or a plain URL. Previews work in task descriptions, comments, Docs, and Chat. Hover and use the ellipsis to change the preview type.
Which plan do you need?
| Capability | Plan |
|---|---|
| GitHub integration, personal and Workspace connections, task linking | Every plan |
| Custom task IDs | Business and above |
| GitHub Automations | Business, Business Plus, and Enterprise |
GitHub Automations use the same trigger and action shape as other ClickUp automations. Documented triggers include pull request merged, branch merged, commit, pull request review created or updated, CI/CD status changed, and a pull request, branch, or commit being linked. Conditions, such as "only when the base branch is main" or "only when the pull request has this label," are on Business and above. Actions apply to tasks that are already linked, except Create Task, which makes a new task. An owner or admin has to turn on the Automations ClickApp, and you need admin rights on the GitHub repository to set the automation up.
Our prices, checked October 2026: Unlimited is $7 per user per month billed annually ($10 monthly). Business is $12 per user per month billed annually ($19 monthly). A team that only pastes task IDs into branch names can stay on Free Forever or Unlimited. A team that wants the task to move to In Review when the pull request opens, and to Done when it merges, should price Business. The numbers are in ClickUp pricing.
Jira remains the closer fit when the engineering org already runs on Jira, Bitbucket, and Confluence and the rest of the company does not need the same tool. ClickUp vs Jira is that comparison. ClickUp is the better single Workspace when product, design, and engineering share the task the pull request closes.
Disconnect a single repo from GitHub Settings with Delete from ClickUp. Disconnect the Workspace connection from the Workspace tab, the menu next to Connected, then Disconnect. Help says those steps do not remove anyone's access to the repository inside GitHub itself.
ClickUp
All-in-one work management for tasks, docs, goals and team collaboration, with a generous free plan.
Affiliate link. We may earn a commission at no extra cost to you. Read our affiliate disclosure
Frequently asked questions
Does ClickUp integrate with GitHub?
Yes. The integration is on every plan. It links commits, branches, and pull requests to tasks in a Space that is connected to the repository. It does not give ClickUp users access to the code.
How do you link a GitHub pull request to a ClickUp task?
Include a task ID in the pull request title, description, branch name, or commit message. Accepted forms include #1abc2de, CU-1abc2de, and a custom task ID such as eng-123. You can also paste the GitHub link from the task.
Who can connect GitHub to a ClickUp Space?
A repository admin adds the repository. A Workspace owner or admin attaches it and links it to Spaces. Members can create a personal connection. Guests and limited members cannot use the integration.
Can GitHub change a ClickUp task status?
Yes, with a Workspace connection. Add the status in square brackets with no space, such as #ud5b[ready], in the commit or pull request message. GitHub Automations that react to a merge start on Business.
Do custom task IDs work with GitHub?
Yes, once custom task IDs exist. Help says ordinary task IDs are on every plan, and custom task IDs such as a team prefix start on Business.