GitFlic CI integration

GitFlic is a Russian Git hosting platform with its own CI/CD engine. Exlogare integrates with it the same way as with GitLab / GitHub / Bitbucket: an OAuth-bound connection drives project listing and token refresh, and a per-project webhook fires on PIPELINE_FAIL to feed us failed pipelines.

Cloud or self-hosted

Both flavours are supported. The differences:

	Cloud (gitflic.ru)	Self-hosted
REST API base	https://api.gitflic.ru	{base_url}/rest-api
OAuth host	https://oauth.gitflic.ru	usually the same as base_url
Auth header	Authorization: token <token>	same

Register an OAuth application

1. In GitFlic open Settings → Personal access tokens → OAuth applications.
2. Create a new application.
3. Redirect URL: https://api.exlogare.net/api/integrations/gitflic/oauth/callback.
4. Scopes: PROJECT_READ, PROJECT_WRITE, USER_READ.
5. Save and copy the client_id and client_secret.

Connect from the dashboard

1. Open Dashboard → Integrations and find the GitFlic section.
2. Enter your base_url (defaults to https://gitflic.ru) and click Connect GitFlic. The wizard redirects you to GitFlic for authorisation and back.
3. Click Sync projects to list the projects your account owns and pick which ones to watch. Each watched project gets a fresh PIPELINE_FAIL webhook registered automatically.

Manual webhook (advanced)

If you’d rather wire the hook by hand (for example to share one connection across many projects), POST to:

{base_url}/rest-api/project/{owner}/{alias}/setting/webhook
Authorization: token <pat-or-oauth-token>
Content-Type: application/json

{
  "url": "https://api.exlogare.net/webhook/gitflic?secret=<random>",
  "secret": "<random>",
  "events": { "PIPELINE_FAIL": true }
}

The ?secret= query string is verified against the per-connection secret stored encrypted in Exlogare.

What happens on a failure

When GitFlic posts PIPELINE_FAIL we resolve the failing job, pull its primary .log artifact from /project/{owner}/{alias}/cicd/job/{job_id}/artifact/{uuid}/download, and run the analysis pipeline. The resulting RCA is delivered through your configured notification channels (Slack / Telegram / Matrix). Posting back as a Merge Request comment isn’t part of the MVP yet — the notification channels carry the full report plus a deep link to the pipeline.