GitLab is currently in Open Beta. The info in this article is subject to change.
Connecting Stitch to GitLab is a four-step process:
Verify that you have access to any projects you want to replicate data from. Stitch is only able to access the same projects as the person who creates the integration.
Stitch. This will allow you to easily identify what application is using the token.
stitch_gitlabin the data warehouse. This schema is where all the tables for this integration will be stored.
stitch, there are two projects to track:
stitch-docs. To track them, you’d enter them like this:
The Sync Historical Data setting will define the starting date for your GitLab integration. This means that data equal to or newer than this date will be replicated to your data warehouse.
Change this setting if you want to sync data beyond GitLab’s default setting of 1 year. For a detailed look at historical syncs, check out the Syncing Historical SaaS Data article.
The Replication Frequency controls how often Stitch will attempt to replicate data from your GitLab integration. By default the frequency is set to 30 minutes, but you can change it to better suit your needs.
Note that the more often GitLab is set to replicate, the higher your row count will be. Even if all the tables in your GitLab integration use Incremental Replication, replicating data frequently will increase your usage.
Stitch & Replicating GitLab Data
Before setting the Replication Frequency, we recommend checking out the structure & Replication Methods for this integration’s tables. Tables that contain nested structures and/or use Full Table Replication will lead to a higher number of replicated rows.
To help prevent overages, we recommend setting the Replication Frequency to something less frequent - like 6 hours instead of 30 minutes.
For more tips on reducing your row count, check out the Reducing Your Row Count article.
After setting the Replication Frequency, click Save Integration to wrap things up.