Connect a repository to FISYCO: GitHub, GitLab, Bitbucket

Name: Connect a repository
Uploaded: 2026-09-30T11:39:38.688Z
Duration: 1 min 12 s
Description: Connect a repository

A project's repository is where FISYCO delivers pull requests for the project's libraries. This page connects one, sets the branch those pull requests target, and shows how FISYCO keeps track of them. GitHub, GitLab (gitlab.com) and Bitbucket Cloud are supported.

The design system reads code from a repository you choose when you connect the design system. It can be this repository or a different one.

Before you start

You're a maintainer of the project, or a workspace owner or admin. Other roles can't open project settings.
For GitHub, you can install a GitHub App on the account or organisation that owns the repository, or you can ask someone who can.

Connect the repository

Open the project, then Settings → Integrations.
In the Repository block, click Continue with GitHub, Continue with GitLab or Continue with Bitbucket.
Give access:
- GitHub: if the workspace already has the app installed, the project joins that installation straight away. Otherwise GitHub opens: install the app, pick the repositories FISYCO may use, and you return to the project.
- GitLab and Bitbucket: sign in with the provider and allow access. If the block shows Authorize, click it first. FISYCO then lists the repositories your account can link.
Choose the repository in the Repository field and click Save.
Optionally choose the Target branch and click Save again.

Until setup is finished, the block shows where you are: Provider, Access, Repository. If your GitHub organisation requires an owner to approve apps, you'll see Installation request sent. The connection appears once the owner approves.

You can also connect a repository while creating a project, or skip that step and connect it here later.

Choose the target branch

Pull requests are opened against the Target branch. If you don't choose one, FISYCO uses the repository's default branch, marked (default) in the list.

The field becomes active after the repository is saved, because branches are loaded from the saved repository. If you switch to another repository, the branch resets to that repository's default branch. Save first, then pick a branch.

Whose access the project uses

The Repository block always shows which access the project works with:

Provider	Access	The block says
GitHub	the GitHub App installation; no personal token is stored	Uses the GitHub App installation
GitLab, Bitbucket	a resource access token set in workspace settings, Connections	Uses the resource access token
GitLab, Bitbucket	without a resource token, the personal access of the person who connected it	Uses the personal access of and their name

A connection belongs to the workspace, so several projects can share one access. If personal access expires or is revoked, the block shows Action needed with the reason. The person whose access it is can click Renew access. If it isn't yours, Take over moves the connection to your own access.

Reinstall the GitHub App

Reinstall GitHub App always opens GitHub, even when the installation works. Use it to give the app access to more repositories or to install it on another organisation.

What happens when you come back:

The same installation keeps its one workspace connection, and FISYCO marks it active again. It doesn't create a duplicate. An installation on another organisation becomes a separate connection.
Check the Repository field. If it's empty, choose the repository again and click Save.

FISYCO also tells you when a reinstall is needed. If the app loses access to the project's repository, the block says so and offers Reinstall GitHub App next to the message. If the app is uninstalled on GitHub, FISYCO unlinks the repository from the projects that used it. Install GitHub App then starts a fresh installation.

Webhooks and their health

Webhooks tell FISYCO when a delivered pull request is opened, merged or closed, so its status in the project stays current without a refresh.

GitHub: one webhook belongs to the GitHub App itself, so nothing is registered per repository.
GitLab and Bitbucket: FISYCO registers a webhook on the repository when you save it. If registration fails, FISYCO retries every five minutes.

Registered webhooks lists the project's webhooks, including Figma's. Each one shows Healthy, Broken or Not checked yet, and when it was last checked. Every five minutes FISYCO asks the provider whether the hook still exists and works, instead of trusting what it saved. It also notices when deliveries arrive but have to be rejected.

When a hook breaks, pull request updates aren't lost. FISYCO reads the status of open pull requests itself every 30 seconds, until a check finds the hook working again. The Repository block shows Action needed with the reason and a button to fix it, and you get a notification.

Change or disconnect

Change the repository or branch in the same form and click Save once. A new repository gets a new webhook. A new branch keeps the existing one.
Disconnect removes the webhooks first, then unlinks the repository from this project. The workspace connection stays, because other projects may use it.

If you connect a repository to a project that already has libraries, the next delivery treats each library as new. The first pull request contains the full library.