← All guides

Integrations and AI · Taskending editorial team

How to connect a GitHub repository to Taskending

Signing in with GitHub and connecting a project repository are separate actions. Repository access is authorized separately to associate code events with work.

· 1 min read

How to apply it

Open Git settings as a company owner or administrator. Choose the GitHub connection flow and review provider permissions. Select a repository you administer and the Taskending project. Supported events arrive through a signed webhook once configured.

A concrete example

Connect the web repository to the Web platform project. A branch or pull request containing WEB-24 helps associate development with the right issue. Document repository-to-project mapping when several repositories are involved.

What to watch for

The current OAuth integration uses broad repo scope. Creating a webhook only in the selected repository does not narrow the token’s provider-level access to that repository. Do not describe it as granular GitHub App access. A linked sign-in account alone may not enable repository events.

How to check the outcome

Verify the selected repository and project, then inspect a real authorized event on its issue. A connected label alone is not end-to-end delivery evidence.

Try it in your own workflow.

Create a company workspace and your first issue. Taskending is currently free.

Start for free

Keep reading

01
Integrations and AI

AI task management with Codex and MCP

Connect Codex to issue context through MCP. A human-reviewed workflow for assigned tasks, progress notes, status updates and time tracking.

02
Integrations and AI

Use issue keys in Git branch names

An issue key connects a code change with its reason. Consistent use in branch names makes context easier to find.

03
Integrations and AI

How to associate Git pushes with issues

A push shows that code reached a repository. Taskending’s connection can associate that event with an issue through its key.