Skip to main content
A private repository is reachable only through a Seyval GitHub App installation that covers it. Connecting your GitHub account is a separate thing: it lets Seyval list your repositories and act on your behalf, but on its own it does not grant access to a private repository the App is not installed on.

​
Which one do I need?

Both are set up in the Dashboard under Settings → GitHub Integration (GitHub連携). GitHub integration settings

​
Install the Seyval App

Required for every private repository, and for push / pull request webhooks.
  1. In Settings → GitHub Integration, click Install Seyval App.
  2. Choose the account or organization that owns the repository.
  3. Choose which repositories the installation covers. A repository left out of that selection stays invisible to Seyval even though the App is installed on the account.
You need permission to install Apps on the target account. For an organization you do not own, GitHub records an install request for the organization owners; access starts once they approve it. One installation belongs to one workspace. If the App is already installed on that account for a different workspace, remove the existing link there first — Seyval will not silently move it.

​
Connect your GitHub account

  1. In Settings → GitHub Integration, click Connect GitHub (GitHub連携をする).
  2. Review the permissions on GitHub’s authorization page and click Authorize.
This connection is what populates the repository picker with the repositories you can see. It is issued by the Seyval GitHub App as a user authorization, so its reach never exceeds the App’s installations — connecting does not, by itself, make a private repository accessible.

​
”Repository not found” when registering a private repository

GitHub answers “does not exist” and “you are not allowed to see it” with the same 404, so Seyval cannot tell them apart. If the URL is correct, the cause is one of:
  • the Seyval App is not installed on the account that owns the repository, or
  • the repository is not included in that installation’s repository selection.
Install the App or add the repository to the installation, then register it again. Connecting or re-connecting your GitHub account does not fix this case.

​
Re-connecting

GitHub access tokens issued for the account connection expire. Seyval renews them automatically in the background, so you normally never notice. If the renewal itself becomes impossible — for example you revoked the authorization on GitHub, or the connection sat unused past its refresh window — the GitHub Integration section shows Re-authentication required (要再連携). Click Re-connect (再連携する) there to restore access. You do not need to disconnect first. Repositories accessed through the Seyval GitHub App are unaffected by this.