Connecting Timequip to GitHub

The Timequip GitHub integration links pull requests, branches, commits, and CI activity to the Timequip task they belong to. Timequip remains the source of truth for tasks; GitHub Issues are not copied into Timequip.

Before you begin

• You need an Account Owner or Admin role to install the GitHub App. See Account Roles: Owner, Admin, Member.
• You need a Project Leader or account Admin role to connect repositories and configure workflow automation. See Project Roles: Leader, Editor, Viewer.
• Your project needs a task key, such as APP. Timequip task keys use that prefix, for example APP-42. See Setting Up a New Project.

Install the GitHub App

1. In Timequip, switch to the account that owns the project.
2. Open Account Settings.
3. Open Git integrations and select Install GitHub App.
4. GitHub opens in a new tab. Choose the organization or personal account, then choose the repositories that Timequip may access.
5. Complete installation and return to Timequip. The connection appears in the Git integrations list.

Connect repositories to a project

1. Open the target project and select Project Settings.
2. Open Git repositories.
3. Select the GitHub connection, choose a repository, and click Connect.
4. Repeat for each repository that belongs to the project. A project can use multiple repositories.

Link development work to a task

Add the task key to a branch name, commit message, pull request title, or pull request description. Matching is case-insensitive.

• Branch: feature/APP-42-github-integration
• Commit: APP-42 Add webhook validation
• Pull request: APP-42 Connect GitHub repositories

Open the task in Timequip and use the Development section to see its linked pull requests, commits, branches, authors, and CI state.

Automate workflow transitions

In Project Settings → Git repositories, choose an active status for a pull request opened or reopened event and a closed status for a merge event, then select Save automation. Automation stays off until you select statuses.

When a pull request is merged, Timequip does not close a task while another linked pull request or merge request is still open. Closing a pull request without merging it does not move the task.

Privacy and troubleshooting

Timequip adds one updateable check and comment to a linked pull request. By default, it shows only the task key and a Timequip link; task title, status, and assignee are not exposed to GitHub unless a project administrator explicitly enables metadata exposure.

• If a repository is missing, confirm that it was selected during GitHub App installation and reconnect the App if needed.
• If a task does not appear, check that the project key and numeric task key are present, for example APP-42.
• If transitions do not run, confirm that both automation statuses are selected in Project Settings.

Using GitLab too? See Connecting Timequip to GitLab.