A project's repository is where FISYCO delivers pull requests for its libraries, and the code it reads to find drift and bypasses. This page connects one. GitHub, GitLab (gitlab.com) and Bitbucket Cloud are supported.
Before you start
- You're a maintainer of the project, or a workspace owner or admin.
- For GitHub, you can install a GitHub App on the organisation or account that owns the repository, or you can ask someone who can.
Connect the repository
- Open the project, then Settings → Integrations.
- In Repository, choose a provider.
- Give access:
- GitHub: click Install GitHub App and pick the repositories FISYCO may use. You return to the project when the installation is done.
- GitLab and Bitbucket: click Authorize and sign in. FISYCO uses your personal access to list the repositories you can link.
- Choose the repository, then click Save.
- Optionally set the Target branch. Pull requests are opened against it. Leave it empty to use the repository's default branch. Branches appear after the repository is saved.
You can also connect a repository while creating a project, or skip that step and connect it later.
Whose access is used
The Repository block always shows which access the project works with:
A connection belongs to the workspace, so several projects can reuse one access. If a personal access expires or is revoked, the project shows what's wrong and how to fix it: sign in again, or let an admin take the connection over.
Webhooks
When the repository is saved, FISYCO registers a webhook so it hears about pushes and pull requests. That's how the status of a delivered pull request stays current, and how the code index updates after a push. The live state of each hook is shown under Registered webhooks. If a hook stops working, FISYCO falls back to checking on a timer until it's repaired.
Change or disconnect
- Change the repository or branch in the same form and save once. Changing the branch doesn't re-register the webhook.
- Disconnect removes the webhooks first, then unlinks the repository from the project. The workspace connection stays, because other projects may use it.
If a repository is connected to a project that already has libraries, the next sync treats everything as new, so the first pull request contains the full library.