# From GitHub or GitLab

> Link your GitHub or GitLab account, connect Fransys continuous integration, and what to do when a commit doesn't show up.

Source: https://docs.fransys.cloud/en/projets/github-gitlab/ Checked against the console on 2026-10-23.

## Link your account

In the service panel, with the code origin set to GitHub or GitLab, click **Link GitHub** (or **Link GitLab**). Fransys only uses this account to import your code and set up continuous integration.

- **Several linked accounts**: choose the one for this service.
- **A repository is missing**: **Allow other repositories** reopens the authorisation at GitHub or GitLab so you can pick the repositories Fransys can access.
- **Managing your accounts**: in **My account**, under code accounts.

If a service's account is no longer linked (unlinked, or access revoked at GitHub or GitLab), the console flags it in the service: link it again.

## Connect continuous integration

Click **Connect CI**. Fransys opens a merge request that adds its pipeline to your repository. Once it's merged, each push builds the image and deploys it.

1. Create the merge request.
2. Follow its instructions.
3. Check that it's merged.
4. Wait for the pipeline to finish: your latest commit then shows up in the service.

What the merge request does:
- your code isn't changed;
- Fransys adds its own CI files, without touching what's already there;
- environment variables prefixed with `FRANSYS_` are added to the repository.

No merge request on your repository? **Re-create the merge request**.

## Latest commit not imported

If your code still isn't imported 10 minutes after your latest commit:
- check the log of the latest CI job in your repository;
- check that Fransys still has access to the repository, in **My account**;
- if the problem persists, write to the team from the help button.

## Build-time variables

Variables read at build time (for example `VITE_…`) aren't passed on by Fransys CI yet. Keep them in your code, or read them at startup.