Enable a provider repository
A provider repository holds the workflows you offer as services. You need the Provider or Both persona, and admin permission on the repository.
Enable a repository
Section titled “Enable a repository”- Go to Provider → Repos. Use the filters Show (All Repos, Enabled Only, Disabled Only) and Owner (All Owners or one owner) to find the repository.
- Turn on the repository’s toggle in the Actions column.
- What happens next depends on the repository:
- App installed and your admin rights confirmed: it’s enabled straight away (owner/repo enabled as Provider).
- Enabled before: the Re-activate Repository dialog opens. Choose Re-activate Now.
- Otherwise: you’re sent to GitHub to install the Zekt GitHub App, or to add the repository to it. Choose Only select repositories and pick the repository. Back in Zekt, Processing GitHub Installation confirms GitHub App installation verified!. Choose Complete Repository Setup, and you’ll see Repository enabled successfully!.
When a repository is enabled, Zekt adds a webhook to it so it can see workflow runs. You don’t configure anything in GitHub yourself. See GitHub access for what the App is used for.
Next: whitelist a workflow and shape it into a service.
If enabling fails
Section titled “If enabling fails”| Message | What to do |
|---|---|
| The Zekt GitHub App is not installed on owner/repo… | Select that repository on GitHub’s installation screen, then retry. |
| This installation grants access to all repositories… | In the App’s settings on GitHub, switch to Only select repositories, pick the repository, then retry. |
| The Zekt GitHub App is suspended on owner/repo… | Unsuspend it in GitHub, then retry. |
| Admin permission on owner/repo is required to enable it with Zekt. | Ask a repository admin to enable it, or to give you admin permission. |
| Your GitHub account cannot access owner/repo. | Check that you’re signed in with the right GitHub account. |
| GitHub authorization is missing or expired… / …was revoked or has expired… | Sign in again, or use Profile → GitHub Authorization. |
| The organisation that owns owner/repo requires single sign-on… | Authorize Zekt for that organization in GitHub, then retry. |
| GitHub did not answer for owner/repo. Nothing was changed… | Retry in a minute. |
| GitHub App installation was cancelled or uninstalled. | Start again and complete the installation on GitHub. |
| Repository Already Enabled | Another Zekt account holds it. See one account per repository. |
| Repository Role Conflict | The repository is already a consumer in your account. A repository can have both roles only with Chainlink. |
Disable a repository
Section titled “Disable a repository”Turn off the toggle and confirm with Disable Repository. Zekt removes its webhook from the repository.
Zekt refuses to disable a provider repository while:
- it still has whitelisted workflows. The Cannot Disable Repository dialog sends you to the Workflows tab to remove them first;
- consumers are subscribed to its services;
- one of its services is published in the Directory.