GitHub and GitLab Integration With QuickInfra: How Source Control Triggers Everything

Source control is the trigger point for everything that happens downstream — build, test, deploy. QuickInfra's GitHub and GitLab integrations are built around webhooks and OAuth app permissions, not long-lived personal access tokens that expire at the worst moment.

OAuth App Connection

Go to Manage → Integrations → Source Control. Select GitHub or GitLab and complete the OAuth authorisation flow. QuickInfra is granted repository access (read and webhook management) on the repositories you select during the OAuth flow — it doesn't get access to all your repositories automatically.

Webhook Installation

When you create a CI/CD Pipeline project and link it to a repository, QuickInfra automatically installs a webhook on the selected repo. The webhook fires on push events to the configured branch (usually main or production). You don't configure webhooks manually. If you disconnect the integration or delete the pipeline project, QuickInfra removes the webhook automatically.

Branch-Based Triggers

Each pipeline project has a trigger configuration: which branch, which event (push, pull request, tag). A standard setup has two pipeline projects for one repository: one triggered by pull requests (runs tests, does not deploy), and one triggered by merge to main (runs tests and deploys to development). Production deployment is triggered by a git tag matching a version pattern, with a manual approval gate.

Build Environment Variables

Secrets needed in the build environment — API keys, database connection strings, registry credentials — are defined in the pipeline project's environment variable configuration in QuickInfra. They're injected into the build environment at runtime and never appear in logs. They're not committed to the repository.

GitLab Self-Hosted Support

QuickInfra supports GitLab.com and GitLab self-hosted installations. For self-hosted GitLab, you configure the GitLab instance URL and a system-level access token in the integration settings. The webhook mechanism is the same as for GitLab.com.

Pull Request Status Checks

QuickInfra posts pipeline status back to GitHub/GitLab pull requests. A failed test run shows as a failed status check on the PR. This prevents merging code that breaks the build.