GitHub

In LaunchCal, a launch can follow its work in GitHub: an organization's project, or a repository's milestone. Its status moves when the project's or milestone's does, it shows their progress, and a project's status updates appear on the launch.

Taktoria only reads from GitHub: it never creates, changes or comments on anything there. It is connected as an app installed on your organization rather than as a person, so it sees only the repositories the organization chose, and keeps working whoever connected it.

Only a workspace owner or admin can connect GitHub.

1. Open Settings → Integrations.
2. Under Ticketing systems, select Connect GitHub.
3. On GitHub, install the Taktoria app on the organization, choose which of its repositories it may read, and approve it.

The app asks to read the organization's projects, and its repositories' issues, pull requests and metadata. If an owner of the organization has to approve it first, Taktoria says so: select Connect GitHub again once they have. The card then says which organization it is connected to. Each Taktoria workspace connects one.

Anybody who can edit a launch can link it, sync it or unlink it.

1. Open the launch's Details tab.
2. Under Ticketing project, paste the address of the organization's project, or of the repository's milestone, into Project link.
3. Select Link project.

A project has to be the connected organization's, and a milestone in a repository the app may read. It syncs straight away. A repository, or anything else in GitHub, is kept as a plain link, and so is a link pasted before GitHub is connected, until it is.

An AI assistant connected to LaunchCal, and the REST API, can link, sync and unlink a launch too, under the same rules.

A linked launch is synced once a day until it launches, and whenever somebody selects Sync now.

For a project:

• Status: the project's newest status update says it. On track, at risk or off track is In development (a launch already in Design or Testing stays there), inactive is On hold, and complete is done. With no status update yet, the launch stays in Scoping until one of the project's items is done. A closed project is done, unless it was inactive.
• Progress: the share of its items closed, merged or in a done column.
• Status updates: each becomes one of the launch's updates on its Activity tab, marked From GitHub with a link to it, and the launch's health follows the newest.

For a milestone: open with none of its issues closed is Scoping, open with some closed is In development, and closed is done. Its progress is the share of its issues closed. A milestone has no updates.

When the project or milestone is done, the launch says it is ready and its owners are told. A status you choose in LaunchCal stands until GitHub's changes again. What a sync changes is shown as GitHub's, in the launch's history, in what its owners are sent and in the audit log.

• It never launches anything. A done project or milestone makes the launch ready; somebody still selects Press to launch! once its required reviews are decided.
• It never changes a launch that has launched.
• It never writes to GitHub.
• It never reads a repository the organization did not give it.

Unlink, on the launch's Details tab, stops that launch syncing; what was brought in stays.

Disconnect, in Settings → Integrations, stops every launch syncing from GitHub and ends Taktoria's access at once. Launches keep what they link and everything synced so far, and pick up again once GitHub is connected again. The app stays installed on the organization until one of its owners uninstalls it in the organization's settings on GitHub.

• The project could not be found: it was deleted, or it is somewhere the app cannot see, such as a repository the organization did not give it. An owner of the organization can add the repository to the app's access in its settings on GitHub; or link the current address.
• GitHub turned the connection down: the app was uninstalled or suspended. A workspace owner or admin connects GitHub again in Settings → Integrations.
• The app is waiting for approval: an owner of the organization approves it on GitHub, then select Connect GitHub again.
• GitHub did not answer the last sync: the next sync tries again, or select Sync now later.
• It is kept as a plain link: GitHub is not connected yet, or the address is not an organization's project or a milestone.