Skip to main content

Connect a GitHub repository

Tiden reads a repository through the Tiden GitHub App. When a pull request merges into the repository's primary branch, Tiden checks it against the product's specs and tests. Merges that did not go through a Tiden intent branch appear on the Branches page under Untracked merges.

Install the Tiden GitHub App​

You can start the installation in Tiden or on GitHub. Both paths end with the App connected to your Tiden workspace.

Start in Tiden​

  1. Open a product.
  2. Select Settings, then Repositories.
  3. Select Keep in sync.
  4. Pick the repository. If the App is not installed yet, GitHub opens and asks you to install it on the account that owns the repository.
  5. Confirm the installation on GitHub. GitHub returns you to Tiden, and the repository appears in the list.

Start on GitHub​

  1. Open the Tiden GitHub App and select Install.
  2. Choose the account and the repositories.
  3. GitHub returns you to Tiden. Sign in if Tiden asks you to.
  4. Check the GitHub account and the workspace that Tiden shows, then select Connect.

Tiden connects the installation only after you select Connect. To stop without connecting, close the page.

After the connection, open Settings, then Repositories in each product that should follow a repository.

GitHub shows the permissions the App requests before you install it. You can change the repositories the App can see at any time in your GitHub account's Settings, under Applications.

Fix "The repository connection is unavailable"​

This message appears in Processing history when a pull request merged while Tiden had no working connection to its repository. Tiden keeps the merge and waits.

  1. In the processing details, select Open repository settings.
  2. Select Keep in sync for the repository and complete the installation.
  3. Return to the merge in Processing history.
    • If the details show Retry, select it. Tiden processes the merge again.
    • If the details say that processing resumes automatically, no action is needed. Tiden picks the merge up within 15 minutes.

Dismiss a merge Tiden cannot identify​

Some merges from before the repository was connected cannot be matched to a single pull request, or to the repository's primary branch at the time. Their details offer Dismiss.

Dismiss closes the record without changing specs or tests. The merge stops counting toward Needs attention. A dismissed record stays in Processing history and is not processed again, even if GitHub sends the event again later.