GitLab
Issues, merge requests and milestones from GitLab.com or a self-hosted GitLab.
What Claro Historia reads
- Issues
- Merge requests
- Milestones
Access is read-only. Claro Historia does not create, change or delete anything in GitLab.
Permissions requested
read_api: read projects, issues and merge requests.read_user: identify the connected account.
Before you start
- GitLab is connected once for the workspace, by an admin. Claro Historia can only read projects that account can already access.
- For a self-hosted GitLab, enter its URL when you connect. It must be reachable from Claro Historia’s servers over the internet.
- If your GitLab group restricts third-party applications, a group owner may need to approve Claro Historia first.
Connect GitLab (workspace admin)
- Open Workspace Settings → Sources.
- Under Code & Repos, find GitLab. For a self-hosted GitLab, enter the Instance URL; leave it blank for GitLab.com.
- Click Connect GitLab, then Authorize on the GitLab page.
- You return to Claro Historia and the card shows Connected.
Add GitLab projects to a project
- Open the project and go to Project Settings → GitLab.
- Click + Add Repo and click a GitLab project to link it.
- Content syncs with the next run, or click Sync in Project Settings → Sync.
Anything synced into a project can be seen by every member of your workspace, because every member can open every project. That includes people who cannot open the original file or message in the source tool. Only link sources you are comfortable sharing with your whole workspace.
Disconnect
- For a project: click Remove next to a repository in Project Settings → GitLab.
- For the workspace: in Workspace Settings → Sources, click Disconnect on the GitLab card.
Disconnecting stops syncing and removes Claro Historia’s access immediately. To have content that was already synced removed as well, email support@clarohistoria.com. See Data and security for how long data is kept.
Problems?
See Troubleshooting or email support@clarohistoria.com.