Specsight now reads code from GitLab as well as GitHub. Paste an access token from GitLab.com or your own instance on the new Integrations page, pick GitLab during onboarding or when creating a project, and Specsight warns by email before a token expires or when GitLab stops accepting it.
New
Changes how the product connects to other tools, like a sync, a webhook or an export another system reads. Customers who built on it may need to update their setup.The new project form now lists repositories from GitLab as well as GitHub, with a Connection choice when both are connected.
Projects on GitLab repositories sync when new code arrives, and the changelog links each code change to the GitLab instance.
Admins and developers can connect GitLab.com or their own instance by pasting an access token, which is checked with GitLab before it is saved.
Connections show Token expiring or Reconnect needed, and Replace token restarts syncing for every project the new token can reach.
Admins and developers get emails when a GitLab token is 30, 7 or 1 days from expiring, and when GitLab stops accepting it.
Changed
The Integrations page shows a card for each service, with its connection status and a Connect, Manage, Replace token or Reconnect button.
Onboarding now has a Codebase step after creating an organisation, where people choose GitHub or GitLab, or choose Not now to connect later.
Project pages and the onboarding Project step now show banners with Reconnect or Open Integrations buttons when a connection cannot list repositories or access is lost.
When no repositories are available, the picker explains how to grant some, from the GitHub install or by giving the token's account Maintainer access to a group.