# GitLab (v1)

Information note **GitLab is supported by the Singer community**   
This integration is powered by [Singer's](https://www.singer.io/) GitLab tap. For support, [visit the GitHub repo](https://github.com/singer-io/tap-gitlab) or [join the Singer Slack](https://singer-slackin.herokuapp.com/).

## GitLab integration summary

Stitch’s GitLab integration replicates data using the [GitLab REST API](https://docs.gitlab.com/ee/api/README.html). Refer to the [Schema](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#schema) section for a list of objects available for replication.

## GitLab feature snapshot

A high-level look at Stitch's GitLab (v1) integration, including release status, useful links, and the features supported in Stitch.

| **STITCH** |  |  |  |
| --- | --- | --- | --- |
| **[Release status](https://help.qlik.com/en-US/stitch/integrations/identify-an-integration-version)** | Released on March 1, 2017 | **Supported by**<br><br>the Info icon<br><br>Indicates if the integration is supported by Stitch or the Singer community. | [Singer Community](https://www.singer.io/) |
| **Stitch plan**<br><br>the Info icon<br><br>The type of Stitch plan required to use the integration. | Standard | **[API availability](https://help.qlik.com/en-US/stitch/developers/stitch-connect/guides/source-destination-reference)**<br><br>the Info icon<br><br>Indicates if the integration is available as a source in Stitch Connect. | the Success icon<br><br>This version of the integration is available via the API.<br><br><br>Available |
| **Singer GitHub repository** | [singer-io/tap-gitlab](https://github.com/singer-io/tap-gitlab) |  |  |
| **REPLICATION SETTINGS** |  |  |  |
| **[Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling where an integration's Replication Frequency is anchored to a time you select. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Advanced Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling)**<br><br>the Info icon<br><br>A type of replication scheduling that allows you to specify granular start times for data extraction using cron expressions. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **Table-level reset**<br><br>the Info icon<br><br>Indicates if data can be reset at the table level. If unsupported, data can only be reset at the integration level. | the Remove icon<br><br>Table-level resets are not supported for this integration. Resets are only supported at the integration level.<br><br><br>Unsupported | **[Configurable Replication Methods](https://help.qlik.com/en-US/stitch/replication/replication-methods)**<br><br>the Info icon<br><br>Indicates if Replication Methods can be defined by you for tables in the integration. | the Remove icon<br><br>Configurable Replication Methods are not supported for this integration. Stitch will use pre-defined replication methods for tables you set to replicate.<br><br><br>Unsupported |
| **DATA SELECTION** |  |  |  |
| **Table selection**<br><br>the Info icon<br><br>The ability to select individual tables for replication in the Stitch interface. If table selection is unavailable, all tables and all the columns they contain will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **Column selection**<br><br>the Info icon<br><br>The ability to select individual columns for replication in the Stitch interface. If column selection is unavailable, all columns will be set to replicate by default. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |
| **Select all**<br><br>the Info icon<br><br>Indicates if the integration supports selecting all available tables and columns. | the Success icon<br><br>Supported<br><br><br>Supported |  |  |
| **TRANSPARENCY** |  |  |  |
| **[Extraction Logs](https://help.qlik.com/en-US/stitch/replication/extractions/integration-extraction-logs)**<br><br>the Info icon<br><br>Logs detailing the Extraction phase of the replication process for a given integration. Includes error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported | **[Loading Reports](https://help.qlik.com/en-US/stitch/replication/integration-loading-reports)**<br><br>the Info icon<br><br>Reports detailing the Loading phase of the replication process for a given integration. Includes the number of rows loaded for each table and error info, should an error occur. | the Success icon<br><br>This feature is supported for this version of the integration.<br><br><br>Supported |

## Connecting GitLab

### GitLab setup requirements

To set up GitLab in Stitch, you need:

* **Access to any projects you want to replicate data from.** Stitch will only be able to access the same projects as the user who creates the integration.

### Step 1: Create a GitLab token

1. Sign into your GitLab account.
2. Click the **user menu (your icon) &gt; Settings**.
3. Click the **Access Tokens** tab.
4. In the **Name** field, enter `Stitch`. This will allow you to easily identify what application is using the token.
5. In the **Scopes** section, check the **api** box. This will allow Stitch to access your API and replicate your GitLab data.
6. Click **Create Personal Access Token**.
7. The new Access Token will display at the top of the page. **Copy the token before navigating away from the page** - GitLab won’t display it again.

### Step 2: Add GitLab as a Stitch data source

1. [Sign into your Stitch account](https://app.stitchdata.com/).

2. On the Stitch Dashboard page, click the **Add Integration** button.

3. Click the **GitLab** icon.

4. Enter a name for the integration. This is the name that will display on the Stitch Dashboard for the integration; it’ll also be used to create the schema in your destination.

   For example, the name “Stitch GitLab” would create a schema called `stitch_gitlab` in the destination. **Note**: Schema names cannot be changed after you save the integration.

5. In the **API URL** field, enter `https://gitlab.com/api/v4`.

6. In the **Private Token** field, paste the **Personal Access Token** you created in the previous section.

7. In the **Projects** and **Groups to Track** fields, you’ll enter the projects and/or groups you want to track as a **space-separated** list.

   For example: `stitchdata/group-a`, or `stitchdata/project-a stitchdata/project-b`

   **Note**: A value for one of these fields must be provided. Additionally, the way you define these settings determines how some data is replicated:

   * If **groups** are provided but **projects** aren’t, all group projects will be replicated.
   * If **groups** and **projects** are provided, the selected projects of the listed groups will be replicated.
   * If **projects** are provided but **groups** aren’t, all listed projects will be replicated.

### Step 3: Define the historical replication start date

The Sync Historical Data setting defines 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 replicate data beyond GitLab’s default setting of **1 year**. For a detailed look at historical replication jobs, check out the [Syncing Historical SaaS Data](https://help.qlik.com/en-US/stitch/replication/syncing-historical-saas-data-resetting-replication-keys) guide.

### Step 4: Create a replication schedule

Information note Replication schedules affect the time Extraction begins, not the time to data loaded. Refer to the [Replication Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling) documentation for more information.

In the **Replication Frequency** section, you’ll create the integration’s [replication schedule](https://help.qlik.com/en-US/stitch/replication/replication-scheduling). An integration’s replication schedule determines how often Stitch runs a replication job, and the time that job begins.

GitLab integrations support the following replication scheduling methods:

* [Replication Frequency](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/replication-frequency)

* [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/anchor-scheduling)

* [Advanced Scheduling using Cron](https://help.qlik.com/en-US/stitch/replication/replication-scheduling/advanced-scheduling) (Advanced or Premium plans only)

To keep your row usage low, consider setting the integration to replicate less frequently. See the [Understanding and Reducing Your Row Usage guide](https://help.qlik.com/en-US/stitch/getting-started/understanding-stitch-usage) for tips on reducing your usage.

### Step 5: Set objects to replicate

Information note **Is an object missing or not replicating?** Verify that the object meets the requirements for [selection](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#selection-requirements) and [replication](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#replication-requirements).

The last step is to select the tables and columns you want to replicate. [Learn about the available tables for this integration.](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#schema)

**Note**: If a replication job is currently in progress, new selections won’t be used until the next job starts.

* Selection options
* Individual tables and columns
* All tables and columns

For GitLab integrations, you can select:

1. **Individual tables and columns**

2. **All tables and columns**

Click the tabs to view instructions for each selection method.

1. In the integration’s **Tables to Replicate tab**, locate a table you want to replicate.

2. To track a table, click the **checkbox** next to the table’s name. A blue checkmark means the table is set to replicate.

3. To track a column, click the **checkbox** next to the column’s name. A blue checkmark means the column is set to replicate.

4. Repeat this process for all the tables and columns you want to replicate.

5. When finished, click the **Finalize Your Selections** button at the bottom of the screen to save your selections.

Information note **Important**: Using the **Select All** feature will overwrite any previous selections. However, selections aren’t final until **Finalize Your Selections** is clicked. Clicking **Cancel** will restore your previous selections. Refer to the [Select All guide](https://help.qlik.com/en-US/stitch/replication/extractions/data-selection/setting-tables-and-columns-to-replicate#set-all-data-to-replicate) for more info about this feature.

1. Click into the integration from the Stitch Dashboard page.

2. Click the **Tables to Replicate** tab.

3. In the list of tables, click the box next to the **Table Names** column.

4. In the menu that displays, click **Track all Tables and Fields**:

   ![The Track all Tables and Fields menu in the Tables to Replicate tab](https://help.qlik.com/en-US/stitch/images/replication/select-all-tables-menu.png)The Track all Tables and Fields menu in the Tables to Replicate tabThe Track all Tables and Fields menu in the Tables to Replicate tab

5. Click the **Finalize Your Selections** button at the bottom of the page to save your data selections.

### Initial and historical replication jobs

After you finish setting up GitLab, its **Sync Status** may show as **Pending** on either the Stitch Dashboard or in the Integration Details page.

For a new integration, a **Pending** status indicates that Stitch is in the process of scheduling the initial replication job for the integration. **This may take some time to complete.**

Information note

**Initial replication jobs with Anchor Scheduling**

If using Anchor Scheduling, an initial replication job may not kick off immediately. This depends on the selected Replication Frequency and Anchor Time. Refer to the [Anchor Scheduling](https://help.qlik.com/en-US/stitch/replication/replication-scheduling#job-scheduling-and-anchor-times) documentation for more information.

#### Free historical data loads

The first seven days of replication, beginning when data is first replicated, are free. Rows replicated from the new integration during this time won’t count towards your quota. Stitch offers this as a way of testing new integrations, measuring usage, and ensuring historical data volumes don’t quickly consume your quota.

Information note **Replication will continue after the seven days are over**. If you’re no longer interested in this source, be sure to **pause** or **delete** the integration to prevent unwanted usage.

## GitLab table reference

Information note

**Schemas and versioning**

Schemas and naming conventions can change from version to version, so we recommend verifying your integration’s version before continuing.

The schema and info displayed below is for **version 1** of this integration.

This is the latest version of the GitLab integration.

Information note

**Table and column names in your destination**

Depending on your destination, table and column names may not appear as they are outlined below.

For example: Object names are lowercased in Redshift (`CusTomERs` &gt; `customers`), while case is maintained in PostgreSQL destinations (`CusTomERs` &gt; `CusTomERs`). Refer to the [Loading Guide](https://help.qlik.com/en-US/stitch/replication/loading/destination-guides) for your destination for more info.

### branches

The `branches` table contains high-level info about repository branches in your projects.

**Note**: To replicate branch data, you must set this table and the [`projects`](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) table to replicate. Data for this table will only be replicated when the associated project (in the [`projects`](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) table) is also updated.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Keys ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | project\_id<br><br>name |
| **Useful links** | [branches schema on GitHub](https://github.com/singer-io/tap-gitlab/blob/master/tap_gitlab/schemas/branches.json "Opens in new tab: branches schema on GitHub")<br><br><br>[GitLab API method](https://gitlab.com/help/api/branches.html#list-repository-branches "Opens in new tab: GitLab API method") |

branches table foreign keys

| Join branches with | on |
| --- | --- |
| [commits](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#commits) | ```<br>branches.project_id = commits.project_id<br>```<br><br>```<br>branches.commit_id = commits.id<br>``` |
| [issues](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#issues) | ```<br>branches.project_id = issues.project_id<br>``` |
| [milestones](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#milestones) | ```<br>branches.project_id = milestones.project_id<br>``` |
| [projects](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) | ```<br>branches.project_id = projects.project_id<br>``` |

branches table schema

| **commit\_id**<br><br><br>STRING |
| --- |
| **developers\_can\_merge**<br><br><br>BOOLEAN |
| **developers\_can\_push**<br><br><br>BOOLEAN |
| **merged**<br><br><br>BOOLEAN |
| **name**<br><br><br>STRING |
| **project\_id**<br><br><br>INTEGER |
| **protected**<br><br><br>BOOLEAN |

### commits

The `commits` table contains info about repository commits in a project.

**Note**: To replicate commit data, you must set this table and the [`projects`](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) table to replicate. Data for this table will only be replicated when the associated project (in the [`projects`](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) table) is also updated.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id |
| **Useful links** | [commits schema on GitHub](https://github.com/singer-io/tap-gitlab/blob/master/tap_gitlab/schemas/commits.json "Opens in new tab: commits schema on GitHub")<br><br><br>[GitLab API method](https://gitlab.com/help/api/commits.md#list-repository-commits "Opens in new tab: GitLab API method") |

commits table foreign keys

| Join commits with | on |
| --- | --- |
| [branches](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#branches) | ```<br>commits.project_id = branches.project_id<br>```<br><br>```<br>commits.id = branches.commit_id<br>``` |
| [issues](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#issues) | ```<br>commits.project_id = issues.project_id<br>``` |
| [milestones](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#milestones) | ```<br>commits.project_id = milestones.project_id<br>``` |
| [projects](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) | ```<br>commits.project_id = projects.project_id<br>``` |

commits table schema

| **allow\_failure**<br><br><br>BOOLEAN |
| --- |
| **author\_email**<br><br><br>STRING |
| **author\_name**<br><br><br>STRING |
| **committer\_email**<br><br><br>STRING |
| **committer\_name**<br><br><br>STRING |
| **created\_at**<br><br><br>DATE-TIME |
| **id**<br><br><br>STRING |
| **message**<br><br><br>STRING |
| **project\_id**<br><br><br>INTEGER |
| **short\_id**<br><br><br>STRING |
| **title**<br><br><br>STRING |

### groups

The `groups` table contains info about the groups in your GitLab account.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id |
| **Useful links** | [groups schema on GitHub](https://github.com/singer-io/tap-gitlab/blob/master/tap_gitlab/schemas/users.json "Opens in new tab: groups schema on GitHub")<br><br><br>[GitLab API method](https://docs.gitlab.com/ee/api/groups.html#list-groups "Opens in new tab: GitLab API method") |

groups table schema

| **avatar\_url**<br><br><br>STRING |
| --- |
| **description**<br><br><br>STRING |
| **full\_name**<br><br><br>STRING |
| **full\_path**<br><br><br>STRING |
| **id**<br><br><br>INTEGER |
| **lfs\_enabled**<br><br><br>BOOLEAN |
| **name**<br><br><br>STRING |
| **path**<br><br><br>STRING |
| **projects**<br><br>ARRAY<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand projects<br><br><table> <tr> <td> <p> <strong>								id							</strong> </p> <p>							INTEGER													</p> </td> </tr> </table> |
| **request\_access\_enabled**<br><br><br>BOOLEAN |
| **visibility\_level**<br><br><br>INTEGER |
| **web\_url**<br><br><br>STRING |

### issues

The `issues` table contains info about issues contained within projects.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id |
| **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | updated\_at |
| **Useful links** | [issues schema on GitHub](https://github.com/singer-io/tap-gitlab/blob/master/tap_gitlab/schemas/issues.json "Opens in new tab: issues schema on GitHub")<br><br><br>[GitLab API method](https://gitlab.com/help/api/issues.md#list-project-issues "Opens in new tab: GitLab API method") |

issues table foreign keys

| Join issues with | on |
| --- | --- |
| [branches](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#branches) | ```<br>issues.project_id = branches.project_id<br>``` |
| [commits](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#commits) | ```<br>issues.project_id = commits.project_id<br>``` |
| [milestones](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#milestones) | ```<br>issues.project_id = milestones.project_id<br>```<br><br>```<br>issues.milestone_id = milestones.id<br>``` |
| [projects](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) | ```<br>issues.project_id = projects.project_id<br>``` |

issues table schema

| **assignee\_id**<br><br><br>INTEGER |
| --- |
| **author\_id**<br><br><br>INTEGER |
| **confidential**<br><br><br>BOOLEAN |
| **created\_at**<br><br>DATE-TIME |
| **description**<br><br><br>STRING |
| **due\_date**<br><br><br>STRING |
| **id**<br><br><br>INTEGER |
| **iid**<br><br><br>INTEGER |
| **labels**<br><br><br>ARRAY<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;. |
| **milestone\_id**<br><br><br>INTEGER |
| **project\_id**<br><br><br>INTEGER |
| **state**<br><br><br>STRING |
| **subscribed**<br><br><br>BOOLEAN |
| **title**<br><br><br>STRING |
| **updated\_at**<br><br>DATE-TIME |
| **user\_notes\_count**<br><br><br>INTEGER |
| **web\_url**<br><br><br>STRING |

### projects

The `projects` table contains info about specific projects.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Key-based Incremental |
| --- | --- |
| **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id |
| **Replication Key ![](https://help.qlik.com/en-US/stitch/images/replication/replication-key-icon.svg)** | last\_activity\_at |
| **Useful links** | [projects schema on GitHub](https://github.com/singer-io/tap-gitlab/blob/master/tap_gitlab/schemas/projects.json "Opens in new tab: projects schema on GitHub")<br><br><br>[GitLab API method](https://gitlab.com/help/api/projects.md#list-all-projects "Opens in new tab: GitLab API method") |

projects table foreign keys

| Join projects with | on |
| --- | --- |
| [branches](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#branches) | ```<br>projects.project_id = branches.project_id<br>``` |
| [commits](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#commits) | ```<br>projects.project_id = commits.project_id<br>``` |
| [issues](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#issues) | ```<br>projects.project_id = issues.project_id<br>``` |
| [milestones](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#milestones) | ```<br>projects.project_id = milestones.project_id<br>``` |
| [users](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#users) | ```<br>projects.creator_id = users.id<br>``` |

projects table schema

| **approvals\_before\_merge**<br><br><br>INTEGER |
| --- |
| **archived**<br><br><br>BOOLEAN |
| **avatar\_url**<br><br><br>STRING |
| **builds\_enabled**<br><br><br>BOOLEAN |
| **container\_registry\_enabled**<br><br><br>BOOLEAN |
| **created\_at**<br><br>DATE-TIME |
| **creator\_id**<br><br><br>INTEGER |
| **default\_branch**<br><br><br>STRING |
| **description**<br><br><br>STRING |
| **forks\_count**<br><br><br>INTEGER |
| **http\_url\_to\_repo**<br><br><br>STRING |
| **id**<br><br><br>INTEGER |
| **issues\_enabled**<br><br><br>BOOLEAN |
| **last\_activity\_at**<br><br>DATE-TIME |
| **lfs\_enabled**<br><br><br>BOOLEAN |
| **merge\_requests\_enabled**<br><br><br>BOOLEAN |
| **name**<br><br><br>STRING |
| **name\_with\_namespace**<br><br><br>STRING |
| **namespace**<br><br><br>OBJECT<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand namespace<br><br><table> <tr> <td> <p> <strong>								id							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								kind							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								name							</strong> </p> <p>							STRING													</p> </td> </tr> <tr> <td> <p> <strong>								path							</strong> </p> <p>							STRING													</p> </td> </tr> </table> |
| **only\_allow\_merge\_if\_all\_discussions\_are\_resolved**<br><br><br>BOOLEAN |
| **only\_allow\_merge\_if\_build\_succeeds**<br><br><br>BOOLEAN |
| **open\_issues\_count**<br><br><br>INTEGER |
| **owner\_id**<br><br><br>INTEGER |
| **path**<br><br><br>STRING |
| **path\_with\_namespace**<br><br><br>STRING |
| **permissions**<br><br><br>OBJECT<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand permissions<br><br><table> <tr> <td> <p> <strong>								group_access							</strong> </p> <p> </p> <p>OBJECT																																</p><div><button><div>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.</div></button></div> <p></p> <div> <button>Click to expand group_access</button><div> <div> <div><div><table> </table></div></div></div> </div></div> </td> </tr> <tr> <td> <p> <strong>								project_access							</strong> </p> <p> </p> <p>OBJECT																																</p><div><button><div>This is a nested data structure. If your destination doesn't natively support nested data, attributes in this object will be flattened into the table. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.</div></button></div> <p></p> <div> <button>Click to expand project_access</button><div> <div> <div><div><table> </table></div></div></div> </div></div> </td> </tr> </table> |
| **public**<br><br><br>BOOLEAN |
| **public\_builds**<br><br><br>BOOLEAN |
| **request\_access\_enabled**<br><br><br>BOOLEAN |
| **shared\_runners\_enabled**<br><br><br>BOOLEAN |
| **shared\_with\_groups**<br><br>ARRAY<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;.<br><br>Click to expand shared\_with\_groups<br><br><table> <tr> <td> <p> <strong>								group_access_level							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								group_id							</strong> </p> <p>							INTEGER													</p> </td> </tr> <tr> <td> <p> <strong>								group_name							</strong> </p> <p>							STRING													</p> </td> </tr> </table> |
| **snippets\_enabled**<br><br><br>BOOLEAN |
| **ssh\_url\_to\_repo**<br><br><br>STRING |
| **star\_count**<br><br><br>INTEGER |
| **tag\_list**<br><br>ARRAY<br><br>This is a nested data structure. If your destination doesn't natively support nested data, attributes will be denested into a subtable. &lt;a href='/en-US/stitch/replication/loading/understanding-loading-row-usage-for-nested-data-structures' target='new'&gt;Learn more&lt;/a&gt;. |
| **visibility\_level**<br><br><br>INTEGER |
| **web\_url**<br><br><br>STRING |
| **wiki\_enabled**<br><br><br>BOOLEAN |

### users

The `users` table contains info about the users in your GitLab account.

| **Replication Method [](https://help.qlik.com/en-US/stitch/replication/replication-methods)[the Info icon](https://help.qlik.com/en-US/stitch/replication/replication-methods)[](https://help.qlik.com/en-US/stitch/replication/replication-methods)** | Full Table |
| --- | --- |
| **Primary Key ![](https://help.qlik.com/en-US/stitch/images/replication/primary-key-icon.svg)** | id |
| **Useful links** | [users schema on GitHub](https://github.com/singer-io/tap-gitlab/blob/master/tap_gitlab/schemas/users.json "Opens in new tab: users schema on GitHub")<br><br><br>[GitLab API method](https://gitlab.com/help/api/users.md#list-users "Opens in new tab: GitLab API method") |

users table foreign keys

| Join users with | on |
| --- | --- |
| [projects](https://help.qlik.com/en-US/stitch/integrations/saas/gitlab#projects) | ```<br>users.id = projects.creator_id<br>``` |

users table schema

| **avatar\_url**<br><br><br>STRING |
| --- |
| **id**<br><br><br>INTEGER |
| **name**<br><br><br>STRING |
| **state**<br><br><br>STRING |
| **username**<br><br><br>STRING |
| **web\_url**<br><br><br>STRING |