Skip to main content

​
Overview

Connecting GitHub brings your engineering delivery into your strategy. Ciclo reads issue data from your repositories so you can:

Live KPIs

Turn repository activity — open issues, bugs, work closed last week — into KPIs that refresh automatically.

Issues as Actions

Link a GitHub issue to an Action so engineering work appears on your board, with sub-issues, labels, and milestone dates carried across.
The sync is read-only (GitHub → Ciclo): Ciclo reads your repositories to populate KPIs and linked Actions, and never changes anything in GitHub.
Connecting and configuring integrations is limited to organisation administrators.

​
Connect GitHub

1

Open Connected Apps

Go to Settings from the account menu, open the Connected Apps tab, find GitHub, and select Connect.
The GitHub row in the Connected Apps settings tab
2

Authorise on GitHub

Ciclo redirects you to GitHub to authorise access to your repositories and issues. Review the request and approve it.
The GitHub OAuth authorisation screen
3

Confirm the connection

You’re returned to Ciclo with a success message, and GitHub shows a green Connected status.

​
Track GitHub KPIs

1

Open the configuration

On the GitHub row, select Configure, then Add New KPI.
The Create New GitHub KPI form
2

Name it and choose a repository

Give the KPI a clear name, then pick the Repository it should measure.
3

Pick a template

Choose a Query Template as a starting point — see the catalogue below.
4

Create the KPI

Select Create KPI. It appears on your Performance page and refreshes automatically.

​
Available GitHub KPIs

Each template gives a useful result as-is — just pick the one you need.
  • Open Issues Count — all open issues in the repository.
  • Open Issues with bug label — open issues labelled bug.
  • Open Issues in Milestone — open issues in a named milestone.
  • Issues Closed Last Week — issues closed in the last 7 days.
  • Inactive Issues — open issues with no activity in the last 30 days.

​
Customising a KPI (optional)

You don’t need any of this to get great results — the built-in templates are designed to be accurate on their own. Pick a template and a repository, and you’re done. Expand the sections below only if you want to fine-tune or go further.
If a template is close but not quite right, you can adjust it instead of starting from scratch. Every KPI has an editable Query field — for example, change the window from the last 7 days to the last 14 days by editing {date-7d} to {date-14d}, or swap the bug label for another. The templates simply fill this field in for you; editing it is optional.
Power users can replace the query entirely using GitHub’s issue search syntax — for example is:issue is:open label:"high priority". Anything GitHub search supports, you can track. For everything that’s possible, see:

GitHub search syntax

The full set of qualifiers you can use to search issues.
1

Open an action and go to Connect

Create or open an Action, then choose Connect.
2

Choose the repository and issue

Select GitHub, pick the repository, then choose the issue to connect. Ciclo fills in the title, description, labels (as tags), any sub-issues (as tasks), and the milestone due date.
Selecting a GitHub repository and issue to connect to an action
3

Save the action

Save, and the action stays connected to the issue.

​
Disconnecting GitHub

Select Disconnect on the GitHub row. Ciclo shows which KPIs and Actions rely on GitHub before you confirm.
Disconnecting preserves history — KPIs keep their recorded values and linked Actions keep their data. They stop syncing until you reconnect, then resume automatically.

Integrations overview

Performance & KPIs

Actions

Connected Apps in Settings