GitLab

Sync projects, issues, merge requests, and commits from GitLab.

Overview
Setup Guide
Permissions
Troubleshooting

Connect Parable to GitLab for comprehensive DevOps and repository data.

Code & MRs

Projects, merge requests, commits

Issues & Planning

Issues, milestones, labels

Data streams

This Provider Plugin defines 13 data streams.

Stream	Description	Sync
`projects`	GitLab projects the authenticated user is a member of	incremental
`groups`	GitLab groups	full
`group_members`	Members of a group (including inherited members)	full
`issues`	Project issues	incremental
`merge_requests`	Project merge requests	incremental
`merge_request_notes`	Notes (comments) on merge requests	incremental
`project_commits`	Project repository commits	incremental
`branches`	Project repository branches	full
`project_members`	Members of a project (including inherited members)	full
`pipelines`	Project CI/CD pipelines	incremental
`repos`	Project repository file tree	full
`branch_commits`	Repository commits for a specific branch	incremental
`commit_diffs`	Diff details for a specific commit	full

What You’ll Need

Credential	What it is
Token	Personal access token with API scope
Base URL	`https://gitlab.com` or your self-hosted GitLab URL

Info: Setup access in GitLab. These steps require Administrator, or a colleague with equivalent permissions who can create credentials for you. If that is not you, ask your GitLab administrator.

Owner or Maintainer role in the group/project
For group-level access, group owner permissions

Step 1: Access User Settings

Log in to GitLab (gitlab.com or your instance)
Click your avatar → Preferences
Navigate to Access Tokens in the sidebar

Step 2: Create Personal Access Token

Click Add new token
Fill in:

Field	Value
Token name	`Parable Integration`
Expiration date	1 year (or per policy)

Step 3: Select Scopes

Enable these scopes:

Scope	Purpose
`api`	Full API access
`read_api`	Read-only API (alternative)
`read_user`	Read user information
`read_repository`	Read repository contents

Tip: For read-only integration, use read_api instead of api.

Step 4: Create and Copy Token

Click Create personal access token
Copy the token immediately

Warning: Copy your personal access token now! This is the only time it will be displayed. Store it in a secure password manager before closing this page.

Step 5: Enter values in the form

Token and GitLab URL: Paste your personal access token and your GitLab instance base URL.
Click Save & test connection.

Test Authentication

curl -H "PRIVATE-TOKEN: YOUR_TOKEN" \
  "https://gitlab.com/api/v4/user"

List Projects

curl -H "PRIVATE-TOKEN: YOUR_TOKEN" \
  "https://gitlab.com/api/v4/projects?membership=true&per_page=5"

Success: Success! If you received a 200 OK response with valid data, your credentials are configured correctly. You can now configure this Provider in Parable.

Tip: Rate Limits: GitLab enforces rate limits of varies; typically 2,000 requests/minute for authenticated users. Parable handles rate limiting automatically with exponential backoff, but initial syncs of large datasets may take longer due to these limits.

Branch Commits

Developer identifier: branch_commitsBranch Commits covers repository commits for a specific branch.

Enables: trace each returned revision to its repository or project, author and committer identities, message, and provider-reported commit times.
Scope: Repository commits for a specific branch; the connector reads /api/v4/projects/{project_id}/repository/commits as an event stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Author Email

Developer identifier: branch_commits.author_emailAuthor Email records email address of the commit author as recorded in Git. It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

Enables: attribute the Branch Commits row to the returned person or account and match the exact author_email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Contact.Email scalar.

Author Name

Developer identifier: branch_commits.author_nameAuthor Name records display name of the commit author as recorded in Git. It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

Enables: attribute the Branch Commits row to the returned person or account and match the exact author_name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row.

Authored Date

Developer identifier: branch_commits.authored_dateAuthored Date records timestamp when the commit was originally authored (may differ from committed date for rebased/cherry-picked commits). It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branch Commits records by authored_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Temporal.DateTime scalar.

Committed Date

Developer identifier: branch_commits.committed_dateCommitted Date records timestamp when the commit was applied to the repository. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branch Commits records by committed_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the connector also declares it for record ordering; the schema assigns the event_time semantic role; the schema uses the Temporal.DateTime scalar.

Committer Email

Developer identifier: branch_commits.committer_emailCommitter Email records email address of the committer as recorded in Git. It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

Enables: attribute the Branch Commits row to the returned person or account and match the exact committer_email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Contact.Email scalar.

Committer Name

Developer identifier: branch_commits.committer_nameCommitter Name records display name of the person who committed the change (may differ from author for applied patches). It is needed to attribute this Branch Commits row to the returned person, account, or organization reference.

Enables: attribute the Branch Commits row to the returned person or account and match the exact committer_name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row.

Created At

Developer identifier: branch_commits.created_atCreated At records timestamp when the commit was created in the repository. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branch Commits records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Temporal.DateTime scalar.

Extended Trailers

Developer identifier: branch_commits.extended_trailersExtended Trailers records extended Git trailers supporting multiple values per key. It is needed to preserve the exact GitLab configuration or execution metadata attached to this GitLab Project Commit record.

Enables: inspect the keys in extended_trailers when reproducing or investigating this record’s configuration, parameters, or execution context.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Generic.JSON scalar; metadata keys and availability follow the GitLab response and can vary by resource type or configuration.

Developer identifier: branch_commits.idID records full SHA-1 hash of the commit, serving as the primary key. It is needed to distinguish repeated deliveries of the same Branch Commits row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Branch Commits and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Last Pipeline

Developer identifier: branch_commits.last_pipelineLast Pipeline records summary of the last pipeline run for this commit, if any. It is needed to preserve the nested last pipeline relationship or details on the parent GitLab Project Commit record.

Enables: expand last_pipeline to connect the containing GitLab Project Commit row to its returned last pipeline entries.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is one nested object per containing GitLab Project Commit object when present.

Created At

Developer identifier: branch_commits.last_pipeline.created_atCreated At records timestamp when the pipeline was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branch Commits records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is interpreted at one GitLab Commit Last Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Developer identifier: branch_commits.last_pipeline.idID records unique numeric ID of the pipeline. It is needed to refer to the same commit last pipeline across records without relying on display text.

Enables: match id to commit last pipeline references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is an identifier, not a measured quantity.

Iid

Developer identifier: branch_commits.last_pipeline.iidIid records project-scoped internal ID of the pipeline. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is an identifier, not a measured quantity.

Ref

Developer identifier: branch_commits.last_pipeline.refRef records branch or tag name the pipeline ran against. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match ref to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is interpreted at one GitLab Commit Last Pipeline record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Sha

Developer identifier: branch_commits.last_pipeline.shaSha records full SHA of the commit the pipeline ran on. It is needed to refer to the same commit last pipeline across records without relying on display text.

Enables: match sha to commit last pipeline references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is an identifier, not a measured quantity.

Source

Developer identifier: branch_commits.last_pipeline.sourceSource records what triggered the pipeline (e.g., push, web, merge_request_event, api, schedule). It is needed to distinguish Branch Commits rows by the exact GitLab-returned source value.

Enables: separate Branch Commits rows by the exact GitLab-returned source label when comparing source.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is interpreted at one GitLab Commit Last Pipeline record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Status

Developer identifier: branch_commits.last_pipeline.statusStatus records current status of the pipeline (e.g., success, failed, pending, running, canceled). It is needed to distinguish Branch Commits rows by the exact GitLab-returned status value.

Enables: separate Branch Commits rows by the exact GitLab-returned status label when comparing status.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is interpreted at one GitLab Commit Last Pipeline record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Updated At

Developer identifier: branch_commits.last_pipeline.updated_atUpdated At records timestamp when the pipeline was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branch Commits records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is interpreted at one GitLab Commit Last Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Web URL

Developer identifier: branch_commits.last_pipeline.web_urlWeb URL records URL to view the pipeline in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Branch Commits record as provenance.
Interpretation: GitLab reports this value on the GitLab Commit Last Pipeline object returned for Branch Commits; it is link at one GitLab Commit Last Pipeline record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Message

Developer identifier: branch_commits.messageMessage records full commit message including title and body. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in message and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.

Parent IDs

Developer identifier: branch_commits.parent_idsParent IDs records SHA hashes of parent commits. Multiple entries indicate a merge commit. It is needed to preserve the nested parent i ds relationship or details on the parent GitLab Project Commit record.

Enables: expand parent_ids to connect the containing GitLab Project Commit row to its returned parent i ds entries.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is one returned collection per containing GitLab Project Commit object.

Project ID

Developer identifier: branch_commits.project_idProject ID records parent project’s numeric id, injected by the ingestion service from the branches tap’s parentContextFields. Absent from the GitLab commits API response body itself. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Short ID

Developer identifier: branch_commits.short_idShort ID records abbreviated SHA hash of the commit for human-readable display. It is needed to refer to the same short across records without relying on display text.

Enables: match short_id to short references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is an identifier, not a measured quantity.

Stats

Developer identifier: branch_commits.statsStats records line-level change statistics for the commit (present when with_stats=true). It is needed to preserve the nested stats relationship or details on the parent GitLab Project Commit record.

Enables: expand stats to connect the containing GitLab Project Commit row to its returned stats entries.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is one nested object per containing GitLab Project Commit object when present.

Additions

Developer identifier: branch_commits.stats.additionsAdditions records number of lines added in this commit. It is needed to measure the GitLab-reported number of lines added in this commit at one GitLab Commit Stats record per row.

Enables: measure and compare the GitLab-reported number of lines added in this commit in additions at one GitLab Commit Stats record per row.
Interpretation: GitLab reports this value on the GitLab Commit Stats object returned for Branch Commits; it is a GitLab-reported count at one GitLab Commit Stats record per row.

Deletions

Developer identifier: branch_commits.stats.deletionsDeletions records number of lines deleted in this commit. It is needed to measure the GitLab-reported number of lines deleted in this commit at one GitLab Commit Stats record per row.

Enables: measure and compare the GitLab-reported number of lines deleted in this commit in deletions at one GitLab Commit Stats record per row.
Interpretation: GitLab reports this value on the GitLab Commit Stats object returned for Branch Commits; it is a GitLab-reported count at one GitLab Commit Stats record per row.

Total

Developer identifier: branch_commits.stats.totalTotal records total number of lines changed (additions + deletions). It is needed to measure the GitLab-reported number of lines changed (additions + deletions) at one GitLab Commit Stats record per row.

Enables: measure and compare the GitLab-reported number of lines changed (additions + deletions) in total at one GitLab Commit Stats record per row.
Interpretation: GitLab reports this value on the GitLab Commit Stats object returned for Branch Commits; it is a GitLab-reported count at one GitLab Commit Stats record per row.

Status

Developer identifier: branch_commits.statusStatus records status of the latest pipeline associated with this commit, if any. It is needed to distinguish Branch Commits rows by the exact GitLab-returned status value.

Enables: separate Branch Commits rows by the exact GitLab-returned status label when comparing status.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is interpreted at one GitLab Project Commit record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Title

Developer identifier: branch_commits.titleTitle records first line of the commit message, typically a summary of the change. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in title and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.

Trailers

Developer identifier: branch_commits.trailersTrailers records key-value pairs parsed from Git trailers in the commit message (e.g., Signed-off-by, Co-authored-by). It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in trailers and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is commit message at one GitLab Project Commit record per row; the schema uses the Generic.JSON scalar; this is only the content included in the GitLab response for this record.

Web URL

Developer identifier: branch_commits.web_urlWeb URL records URL to view the commit in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Branch Commits record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Branch Commits; it is link at one GitLab Project Commit record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Branches

Developer identifier: branchesBranches covers project repository branches.

Enables: inventory returned branches and connect each branch name to its head revision and protection details.
Scope: Project repository branches; the connector reads /api/v4/projects/{id}/repository/branches as a snapshot stream in full mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

Composite ID

Developer identifier: branches._composite_idComposite ID records synthetic primary key formed by joining project_id and branch name with ’:’ for global uniqueness. Injected by the ingestion service. It is needed to refer to the same composite across records without relying on display text.

Enables: match _composite_id to composite references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Can Push

Developer identifier: branches.can_pushCan Push records whether the current authenticated user can push to this branch. It is needed to distinguish Branches rows by the exact GitLab-returned can push value.

Enables: select Branches rows where can_push is true or false when comparing the condition described by Can Push.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Commit

Developer identifier: branches.commitCommit records the latest commit on this branch. It is needed to preserve the nested commit relationship or details on the parent GitLab Branch record.

Enables: expand commit to connect the containing GitLab Branch row to its returned commit entries.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is one nested object per containing GitLab Branch object when present.

Author Email

Developer identifier: branches.commit.author_emailAuthor Email records email address of the commit author. It is needed to attribute this Branches row to the returned person, account, or organization reference.

Enables: attribute the Branches row to the returned person or account and match the exact author_email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row; the schema uses the Contact.Email scalar.

Author Name

Developer identifier: branches.commit.author_nameAuthor Name records name of the commit author. It is needed to attribute this Branches row to the returned person, account, or organization reference.

Enables: attribute the Branches row to the returned person or account and match the exact author_name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row.

Authored Date

Developer identifier: branches.commit.authored_dateAuthored Date records timestamp when the commit was authored. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branches records by authored_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row; the schema uses the Temporal.DateTime scalar.

Committed Date

Developer identifier: branches.commit.committed_dateCommitted Date records timestamp when the commit was committed. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branches records by committed_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row; the schema uses the Temporal.DateTime scalar.

Committer Email

Developer identifier: branches.commit.committer_emailCommitter Email records email address of the committer. It is needed to attribute this Branches row to the returned person, account, or organization reference.

Enables: attribute the Branches row to the returned person or account and match the exact committer_email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row; the schema uses the Contact.Email scalar.

Committer Name

Developer identifier: branches.commit.committer_nameCommitter Name records name of the committer. It is needed to compare the returned committer name for individual Branches rows and select rows with a specific committer_name value.

Enables: locate Branches rows whose returned committer name exactly matches committer_name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row.

Created At

Developer identifier: branches.commit.created_atCreated At records timestamp when the commit was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Branches records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is interpreted at one GitLab Branch Commit record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Extended Trailers

Developer identifier: branches.commit.extended_trailersExtended Trailers records extended git trailer key-value pairs parsed from the commit message, supporting multiple values per key. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in extended_trailers and attribute it to the same record’s repository or project, branch name, revision, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; the schema uses the Generic.JSON scalar; this is only the content included in the GitLab response for this record.

Developer identifier: branches.commit.idID records full SHA hash of the commit. It is needed to refer to the same branch commit across records without relying on display text.

Enables: match id to branch commit references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is an identifier, not a measured quantity.

Message

Developer identifier: branches.commit.messageMessage records full commit message including body. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in message and attribute it to the same record’s repository or project, branch name, revision, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; this is only the content included in the GitLab response for this record.

Parent IDs

Developer identifier: branches.commit.parent_idsParent IDs records list of parent commit SHA hashes. It is needed to preserve the nested parent i ds relationship or details on the parent GitLab Branch Commit record.

Enables: expand parent_ids to connect the containing GitLab Branch Commit row to its returned parent i ds entries.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is one returned collection per containing GitLab Branch Commit object.

Short ID

Developer identifier: branches.commit.short_idShort ID records abbreviated SHA hash of the commit. It is needed to refer to the same short across records without relying on display text.

Enables: match short_id to short references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is an identifier, not a measured quantity.

Title

Developer identifier: branches.commit.titleTitle records first line of the commit message (subject). It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in title and attribute it to the same record’s repository or project, branch name, revision, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; this is only the content included in the GitLab response for this record.

Trailers

Developer identifier: branches.commit.trailersTrailers records git trailer key-value pairs parsed from the commit message. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in trailers and attribute it to the same record’s repository or project, branch name, revision, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is commit message at one GitLab Branch Commit record per row; the schema uses the Generic.JSON scalar; this is only the content included in the GitLab response for this record.

Web URL

Developer identifier: branches.commit.web_urlWeb URL records URL to view the commit in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Branches record as provenance.
Interpretation: GitLab reports this value on the GitLab Branch Commit object returned for Branches; it is link at one GitLab Branch Commit record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Default

Developer identifier: branches.defaultDefault records whether this is the default branch of the repository. It is needed to distinguish Branches rows by the exact GitLab-returned default value.

Enables: select Branches rows where default is true or false when comparing the condition described by Default.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Developers Can Merge

Developer identifier: branches.developers_can_mergeDevelopers Can Merge records whether developers are allowed to merge into this branch. It is needed to distinguish Branches rows by the exact GitLab-returned developers can merge value.

Enables: select Branches rows where developers_can_merge is true or false when comparing the condition described by Developers Can Merge.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Developers Can Push

Developer identifier: branches.developers_can_pushDevelopers Can Push records whether developers are allowed to push to this branch. It is needed to distinguish Branches rows by the exact GitLab-returned developers can push value.

Enables: select Branches rows where developers_can_push is true or false when comparing the condition described by Developers Can Push.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Merged

Developer identifier: branches.mergedMerged records whether the branch has been merged into the default branch. It is needed to distinguish Branches rows by the exact GitLab-returned merged value.

Enables: select Branches rows where merged is true or false when comparing the condition described by Merged.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: branches.nameName records branch name. It is needed to distinguish repeated deliveries of the same Branches row using the declared ingestion key.

Enables: use name as the declared ingestion deduplication key for Branches and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; the connector declares it as an ingestion deduplication key.

Project ID

Developer identifier: branches.project_idProject ID records parent project’s numeric id, injected by the ingestion service from the projects tap’s parentContextFields. Absent from the GitLab branches API response body itself. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Protected

Developer identifier: branches.protectedProtected records whether the branch is protected. It is needed to distinguish Branches rows by the exact GitLab-returned protected value.

Enables: select Branches rows where protected is true or false when comparing the condition described by Protected.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is interpreted at one GitLab Branch record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Web URL

Developer identifier: branches.web_urlWeb URL records URL to view the branch in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Branches record as provenance.
Interpretation: GitLab reports this value on the GitLab Branch object returned for Branches; it is link at one GitLab Branch record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Commit Diffs

Developer identifier: commit_diffsCommit Diffs covers diff details for a specific commit.

Enables: inspect each returned file diff in the context of its repository or project and parent commit.
Scope: Diff details for a specific commit; the connector reads /api/v4/projects/{project_id}/repository/commits/{id}/diff as an event stream in full mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

A Mode

Developer identifier: commit_diffs.a_modeA Mode records unix file mode of the file before the change (e.g., ‘100644’ for regular file, ‘100755’ for executable, ‘000000’ for non-existent). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned a mode value.

Enables: separate Commit Diffs rows by the exact GitLab-returned a_mode label when comparing a mode.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

B Mode

Developer identifier: commit_diffs.b_modeB Mode records unix file mode of the file after the change (e.g., ‘100644’ for regular file, ‘100755’ for executable, ‘000000’ for deleted file). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned b mode value.

Enables: separate Commit Diffs rows by the exact GitLab-returned b_mode label when comparing b mode.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Collapsed

Developer identifier: commit_diffs.collapsedCollapsed records whether the diff was returned in collapsed form (large diffs may be summarized rather than fully expanded). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned collapsed value.

Enables: select Commit Diffs rows where collapsed is true or false when comparing the condition described by Collapsed.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Committed Date

Developer identifier: commit_diffs.committed_dateCommitted Date records timestamp when the parent commit was applied to the repository, injected by the ingestion service from the branch_commits tap’s parentContextFields. Absent from the GitLab commit diff API response body itself. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Commit Diffs records by committed_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is interpreted at one GitLab Commit Diff record per row; the connector also declares it for record ordering; the schema assigns the event_time semantic role; the schema uses the Temporal.DateTime scalar.

Deleted File

Developer identifier: commit_diffs.deleted_fileDeleted File records whether the file was deleted in this commit. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned deleted file value.

Enables: select Commit Diffs rows where deleted_file is true or false when comparing the condition described by Deleted File.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Diff

Developer identifier: commit_diffs.diffDiff records the actual unified diff content showing line-by-line additions and removals. May be truncated for very large diffs. It is needed to measure the GitLab-reported number of diff at one GitLab Commit Diff record per row.

Enables: measure and compare the GitLab-reported number of diff in diff at one GitLab Commit Diff record per row.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is diff at one GitLab Commit Diff record per row; GitLab may omit, collapse, summarize, or truncate this code-change content as noted by the field description.

Generated File

Developer identifier: commit_diffs.generated_fileGenerated File records whether GitLab considers this file to be a generated file (e.g., compiled assets, lock files). It is needed to distinguish Commit Diffs rows by the exact GitLab-returned generated file value.

Enables: select Commit Diffs rows where generated_file is true or false when comparing the condition described by Generated File.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Developer identifier: commit_diffs.idID records synthetic primary key computed by the ingestor from old_path, new_path, diff (sha1). Not part of the upstream API response; written into each row at bronze ingestion time. It is needed to distinguish repeated deliveries of the same Commit Diffs row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Commit Diffs and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

New File

Developer identifier: commit_diffs.new_fileNew File records whether this diff entry represents a newly created file. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned new file value.

Enables: select Commit Diffs rows where new_file is true or false when comparing the condition described by New File.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

New Path

Developer identifier: commit_diffs.new_pathNew Path records new file path after the change. Identifies which files were modified in each commit. Serves as the primary key for this diff entry. It is needed to refer to the same new path across records without relying on display text.

Enables: match new_path to new path references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is an identifier, not a measured quantity; the schema uses the Asset.FilePath scalar.

Old Path

Developer identifier: commit_diffs.old_pathOld Path records original file path before the change. Used to track file renames and moves across commits. It is needed to compare the returned old path for individual Commit Diffs rows and select rows with a specific old_path value.

Enables: trace the old path relationship returned in old_path from the GitLab Commit Diff row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; the schema uses the Asset.FilePath scalar.

Project ID

Developer identifier: commit_diffs.project_idProject ID records parent project’s numeric id, injected by the ingestion service from the branch_commits tap’s parentContextFields. Absent from the GitLab commit diff API response body itself. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Renamed File

Developer identifier: commit_diffs.renamed_fileRenamed File records whether the file was renamed in this commit. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned renamed file value.

Enables: select Commit Diffs rows where renamed_file is true or false when comparing the condition described by Renamed File.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Too Large

Developer identifier: commit_diffs.too_largeToo Large records whether the diff exceeded the API’s size limit and was truncated. When true, only a summary is returned. It is needed to distinguish Commit Diffs rows by the exact GitLab-returned too large value.

Enables: select Commit Diffs rows where too_large is true or false when comparing the condition described by Too Large.
Interpretation: GitLab reports this value on the GitLab Commit Diff object returned for Commit Diffs; it is interpreted at one GitLab Commit Diff record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Group Members

Developer identifier: group_membersGroup Members covers members of a group (including inherited members).

Enables: map the GitLab accounts and memberships represented by Group Members records and trace a returned access assignment to its account or group.
Scope: Members of a group (including inherited members); the connector reads /api/v4/groups/{id}/members/all as a snapshot stream in full mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

Access Level

Developer identifier: group_members.access_levelAccess Level records numeric permission level granted to the member within the group (0=No access, 5=Minimal, 10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). GitLab returns this as an integer, not a string. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact access_level access value with the resource, account, or membership represented by the same Group Members row.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Avatar URL

Developer identifier: group_members.avatar_urlAvatar URL records URL to the member’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Group Members record as provenance.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is link at one GitLab Group Member record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Created At

Developer identifier: group_members.created_atCreated At records timestamp when the user account was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Group Members records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Created By

Developer identifier: group_members.created_byCreated By records user who added this member to the group. It is needed to preserve the nested created by relationship or details on the parent GitLab Group Member record.

Enables: expand created_by to connect the containing GitLab Group Member row to its returned created by entries.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is one nested object per containing GitLab Group Member object when present.

Avatar URL

Developer identifier: group_members.created_by.avatar_urlAvatar URL records URL to the creator’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Group Members record as provenance.
Interpretation: GitLab reports this value on the Member Created By object returned for Group Members; it is link at one Member Created By record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: group_members.created_by.idID records user ID of the creator. It is needed to refer to the same member created by across records without relying on display text.

Enables: match id to member created by references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Member Created By object returned for Group Members; it is an identifier, not a measured quantity.

Name

Developer identifier: group_members.created_by.nameName records display name of the creator. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

Enables: attribute the Group Members row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Member Created By object returned for Group Members; it is interpreted at one Member Created By record per row; the schema uses the Identity.Name scalar.

State

Developer identifier: group_members.created_by.stateState records account state of the creator. It is needed to distinguish Group Members rows by the exact GitLab-returned state value.

Enables: separate Group Members rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the Member Created By object returned for Group Members; it is interpreted at one Member Created By record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: group_members.created_by.usernameUser Name records GitLab username of the creator. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

Enables: attribute the Group Members row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Member Created By object returned for Group Members; it is interpreted at one Member Created By record per row.

Web URL

Developer identifier: group_members.created_by.web_urlWeb URL records URL to the creator’s GitLab profile page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Group Members record as provenance.
Interpretation: GitLab reports this value on the Member Created By object returned for Group Members; it is link at one Member Created By record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: group_members.emailEmail records email address of the member, if visible. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

Enables: attribute the Group Members row to the returned person or account and match the exact email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; the schema uses the Contact.Email scalar.

Expires At

Developer identifier: group_members.expires_atExpires At records membership expiration date if set (YYYY-MM-DD format). It is needed to place the record at the time or date reported for this event or state.

Enables: bound Group Members records by expires_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; the schema uses the Temporal.Date scalar.

Group SAML Identity

Developer identifier: group_members.group_saml_identityGroup SAML Identity records SAML identity information for the member if group SAML SSO is configured. It is needed to preserve the nested group saml identity relationship or details on the parent GitLab Group Member record.

Enables: expand group_saml_identity to connect the containing GitLab Group Member row to its returned group saml identity entries.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is one nested object per containing GitLab Group Member object when present.

Extern Uid

Developer identifier: group_members.group_saml_identity.extern_uidExtern Uid records external UID from the SAML identity provider. It is needed to refer to the same extern uid across records without relying on display text.

Enables: match extern_uid to extern uid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Group Saml Identity object returned for Group Members; it is an identifier, not a measured quantity.

Provider

Developer identifier: group_members.group_saml_identity.providerProvider records name of the SAML identity provider. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare provider among Group Members records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the Group Saml Identity object returned for Group Members; it is interpreted at one Group Saml Identity record per row; the value is a GitLab-returned or configured label at the Group Saml Identity grain rather than a universal taxonomy.

SAML Provider ID

Developer identifier: group_members.group_saml_identity.saml_provider_idSAML Provider ID records ID of the SAML provider configuration in GitLab. It is needed to refer to the same saml provider across records without relying on display text.

Enables: match saml_provider_id to saml provider references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Group Saml Identity object returned for Group Members; it is an identifier, not a measured quantity.

Developer identifier: group_members.idID records user ID of the member. It is needed to distinguish repeated deliveries of the same Group Members row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Group Members and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Is Using Seat

Developer identifier: group_members.is_using_seatIs Using Seat records whether the member is consuming a license seat. It is needed to distinguish Group Members rows by the exact GitLab-returned is using seat value.

Enables: select Group Members rows where is_using_seat is true or false when comparing the condition described by Is Using Seat.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Membership State

Developer identifier: group_members.membership_stateMembership State records state of the membership itself (active, awaiting, etc.). It is needed to distinguish Group Members rows by the exact GitLab-returned membership state value.

Enables: separate Group Members rows by the exact GitLab-returned membership_state label when comparing membership state.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: group_members.nameName records display name of the member. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

Enables: attribute the Group Members row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; the schema uses the Identity.Name scalar.

Override

Developer identifier: group_members.overrideOverride records whether the member’s access level has been overridden from the inherited value. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Group Members rows with the exact override access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: group_members.stateState records account state of the member (active, blocked, etc.). It is needed to distinguish Group Members rows by the exact GitLab-returned state value.

Enables: separate Group Members rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: group_members.usernameUser Name records GitLab username of the member. It is needed to attribute this Group Members row to the returned person, account, or organization reference.

Enables: attribute the Group Members row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is interpreted at one GitLab Group Member record per row.

Web URL

Developer identifier: group_members.web_urlWeb URL records URL to the member’s GitLab profile page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Group Members record as provenance.
Interpretation: GitLab reports this value on the GitLab Group Member object returned for Group Members; it is link at one GitLab Group Member record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Groups

Developer identifier: groupsGroups covers GitLab groups.

Enables: map the GitLab accounts and memberships represented by Groups records and trace a returned access assignment to its account or group.
Scope: GitLab groups; the connector reads /api/v4/groups as a snapshot stream in full mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

Auto Devops Enabled

Developer identifier: groups.auto_devops_enabledAuto Devops Enabled records whether Auto DevOps is enabled by default for projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned auto devops enabled value.

Enables: select Groups rows where auto_devops_enabled is true or false when comparing the condition described by Auto Devops Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Avatar URL

Developer identifier: groups.avatar_urlAvatar URL records URL of the group avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is link at one GitLab Group record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Created At

Developer identifier: groups.created_atCreated At records timestamp when the group was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Groups records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the schema uses the Temporal.DateTime scalar.

Default Branch

Developer identifier: groups.default_branchDefault Branch records default branch name for projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned default branch value.

Enables: separate Groups rows by the exact GitLab-returned default_branch label when comparing default branch.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Default Branch Protection

Developer identifier: groups.default_branch_protectionDefault Branch Protection records default branch protection level for projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned default branch protection value.

Enables: separate Groups rows by the exact GitLab-returned default_branch_protection label when comparing default branch protection.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Default Branch Protection Defaults

Developer identifier: groups.default_branch_protection_defaultsDefault Branch Protection Defaults records default branch protection settings. It is needed to preserve the nested default branch protection defaults relationship or details on the parent GitLab Group record.

Enables: expand default_branch_protection_defaults to connect the containing GitLab Group row to its returned default branch protection defaults entries.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is one nested object per containing GitLab Group object when present.

Allow Force Push

Developer identifier: groups.default_branch_protection_defaults.allow_force_pushAllow Force Push records whether force push is allowed on the default branch. It is needed to distinguish Groups rows by the exact GitLab-returned allow force push value.

Enables: select Groups rows where allow_force_push is true or false when comparing the condition described by Allow Force Push.
Interpretation: GitLab reports this value on the Default Branch Protection Defaults object returned for Groups; it is interpreted at one Default Branch Protection Defaults record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Allowed To Merge

Developer identifier: groups.default_branch_protection_defaults.allowed_to_mergeAllowed To Merge records roles allowed to merge into the default branch. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: expand allowed_to_merge to examine the returned allowed to merge details for the containing Default Branch Protection Defaults record.
Interpretation: GitLab reports this value on the Default Branch Protection Defaults object returned for Groups; it is one returned collection per containing Default Branch Protection Defaults object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Access Level

Developer identifier: groups.default_branch_protection_defaults.allowed_to_merge.access_levelAccess Level records numeric access level (e.g., 30 for developer, 40 for maintainer). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact access_level access value with the resource, account, or membership represented by the same Groups row.
Interpretation: GitLab reports this value on the Access Level Entry object returned for Groups; it is interpreted at one Access Level Entry record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Allowed To Push

Developer identifier: groups.default_branch_protection_defaults.allowed_to_pushAllowed To Push records roles allowed to push to the default branch. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: expand allowed_to_push to examine the returned allowed to push details for the containing Default Branch Protection Defaults record.
Interpretation: GitLab reports this value on the Default Branch Protection Defaults object returned for Groups; it is one returned collection per containing Default Branch Protection Defaults object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Developer Can Initial Push

Developer identifier: groups.default_branch_protection_defaults.developer_can_initial_pushDeveloper Can Initial Push records whether developers can perform the initial push. It is needed to distinguish Groups rows by the exact GitLab-returned developer can initial push value.

Enables: select Groups rows where developer_can_initial_push is true or false when comparing the condition described by Developer Can Initial Push.
Interpretation: GitLab reports this value on the Default Branch Protection Defaults object returned for Groups; it is interpreted at one Default Branch Protection Defaults record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Description

Developer identifier: groups.descriptionDescription records group description text. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s parent record, owner, status, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is description text at one GitLab Group record per row; this is only the content included in the GitLab response for this record.

Duo Features Enabled

Developer identifier: groups.duo_features_enabledDuo Features Enabled records whether GitLab Duo features are enabled. It is needed to distinguish Groups rows by the exact GitLab-returned duo features enabled value.

Enables: select Groups rows where duo_features_enabled is true or false when comparing the condition described by Duo Features Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Emails Disabled

Developer identifier: groups.emails_disabledEmails Disabled records whether email notifications are disabled for the group. It is needed to distinguish Groups rows by the exact GitLab-returned emails disabled value.

Enables: select Groups rows where emails_disabled is true or false when comparing the condition described by Emails Disabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Emails Enabled

Developer identifier: groups.emails_enabledEmails Enabled records whether email notifications are enabled for the group. It is needed to distinguish Groups rows by the exact GitLab-returned emails enabled value.

Enables: select Groups rows where emails_enabled is true or false when comparing the condition described by Emails Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Enabled Git Access Protocol

Developer identifier: groups.enabled_git_access_protocolEnabled Git Access Protocol records allowed Git access protocol (ssh, http, or all). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Groups rows with the exact enabled_git_access_protocol access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Extra Shared Runners Minutes Limit

Developer identifier: groups.extra_shared_runners_minutes_limitExtra Shared Runners Minutes Limit records extra CI/CD minutes limit purchased for the group. It is needed to measure the reported extra shared runners minutes limit for one gitlab group record.

Enables: measure and compare extra_shared_runners_minutes_limit per GitLab Group record in minutes.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; its unit or granularity is minutes.

File Template Project ID

Developer identifier: groups.file_template_project_idFile Template Project ID records project ID used for file templates. It is needed to refer to the same file template project across records without relying on display text.

Enables: match file_template_project_id to file template project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is an identifier, not a measured quantity.

Full Name

Developer identifier: groups.full_nameFull Name records full human-readable name including parent group names separated by slashes. It is needed to compare the returned full name for individual Groups rows and select rows with a specific full_name value.

Enables: locate Groups rows whose returned full name exactly matches full_name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row.

Full Path

Developer identifier: groups.full_pathFull Path records full path including parent groups, used for namespace resolution. It is needed to compare the returned full path for individual Groups rows and select rows with a specific full_path value.

Enables: trace the full path relationship returned in full_path from the GitLab Group row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row.

Full Path With Namespace

Developer identifier: groups.full_path_with_namespaceFull Path With Namespace records alias for full_path including namespace. It is needed to compare the returned full path with namespace for individual Groups rows and select rows with a specific full_path_with_namespace value.

Enables: locate Groups rows whose returned full path with namespace exactly matches full_path_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row.

Developer identifier: groups.idID records unique numeric identifier for the group. It is needed to distinguish repeated deliveries of the same Groups row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Groups and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

IP Restriction Ranges

Developer identifier: groups.ip_restriction_rangesIP Restriction Ranges records comma-separated list of IP address ranges allowed to access the group. It is needed to preserve the GitLab-reported network address context for the same record.

Enables: correlate ip_restriction_ranges with the actor, request, or session on the same GitLab event without treating it as proof of physical presence.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the value is network address context; this GitLab-reported or configured context does not establish residency or verified physical presence; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

LDAP Access

Developer identifier: groups.ldap_accessLDAP Access records minimum LDAP access level for group members. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact ldap_access access value with the resource, account, or membership represented by the same Groups row.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

LDAP Cn

Developer identifier: groups.ldap_cnLDAP Cn records LDAP Common Name linked to this group. It is needed to preserve the exact GitLab-reported business, directory, or identity attribute represented by this field.

Enables: match or segment Groups records by ldap_cn only within the same GitLab attribute contract.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the value is a GitLab-returned or configured label and is not a universal identity or business taxonomy.

Lfs Enabled

Developer identifier: groups.lfs_enabledLfs Enabled records whether Git Large File Storage is enabled. It is needed to distinguish Groups rows by the exact GitLab-returned lfs enabled value.

Enables: select Groups rows where lfs_enabled is true or false when comparing the condition described by Lfs Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Lock Duo Features Enabled

Developer identifier: groups.lock_duo_features_enabledLock Duo Features Enabled records whether the Duo features setting is locked. It is needed to distinguish Groups rows by the exact GitLab-returned lock duo features enabled value.

Enables: select Groups rows where lock_duo_features_enabled is true or false when comparing the condition described by Lock Duo Features Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Lock Math Rendering Limits Enabled

Developer identifier: groups.lock_math_rendering_limits_enabledLock Math Rendering Limits Enabled records whether the math rendering limits setting is locked. It is needed to distinguish Groups rows by the exact GitLab-returned lock math rendering limits enabled value.

Enables: select Groups rows where lock_math_rendering_limits_enabled is true or false when comparing the condition described by Lock Math Rendering Limits Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Marked For Deletion On

Developer identifier: groups.marked_for_deletion_onMarked For Deletion On records date when the group was marked for deletion. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Groups records by marked_for_deletion_on, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the schema uses the Temporal.Date scalar.

Math Rendering Limits Enabled

Developer identifier: groups.math_rendering_limits_enabledMath Rendering Limits Enabled records whether math rendering limits are enabled. It is needed to distinguish Groups rows by the exact GitLab-returned math rendering limits enabled value.

Enables: select Groups rows where math_rendering_limits_enabled is true or false when comparing the condition described by Math Rendering Limits Enabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Membership Lock

Developer identifier: groups.membership_lockMembership Lock records whether membership is locked and cannot be changed by non-owners. It is needed to distinguish Groups rows by the exact GitLab-returned membership lock value.

Enables: select Groups rows where membership_lock is true or false when comparing the condition described by Membership Lock.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Mentions Disabled

Developer identifier: groups.mentions_disabledMentions Disabled records whether mentions are disabled for the group. It is needed to distinguish Groups rows by the exact GitLab-returned mentions disabled value.

Enables: select Groups rows where mentions_disabled is true or false when comparing the condition described by Mentions Disabled.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: groups.nameName records human-readable group name. It is needed to compare the returned name for individual Groups rows and select rows with a specific name value.

Enables: locate Groups rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the schema uses the Identity.Name scalar.

Parent ID

Developer identifier: groups.parent_idParent ID records ID of the parent group, null if top-level. It is needed to refer to the same parent across records without relying on display text.

Enables: match parent_id to parent references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is an identifier, not a measured quantity.

Path

Developer identifier: groups.pathPath records URL-friendly path slug for the group. It is needed to compare the returned path for individual Groups rows and select rows with a specific path value.

Enables: trace the path relationship returned in path from the GitLab Group row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the schema uses the Identity.Slug scalar.

Prevent Forking Outside Group

Developer identifier: groups.prevent_forking_outside_groupPrevent Forking Outside Group records whether forking projects outside the group is prevented. It is needed to distinguish Groups rows by the exact GitLab-returned prevent forking outside group value.

Enables: select Groups rows where prevent_forking_outside_group is true or false when comparing the condition described by Prevent Forking Outside Group.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Project Creation Level

Developer identifier: groups.project_creation_levelProject Creation Level records who can create projects in this group. It is needed to distinguish Groups rows by the exact GitLab-returned project creation level value.

Enables: separate Groups rows by the exact GitLab-returned project_creation_level label when comparing project creation level.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Projects

Developer identifier: groups.projectsProjects records list of projects within the group (when requested). It is needed to preserve the nested projects relationship or details on the parent GitLab Group record.

Enables: expand projects to connect the containing GitLab Group row to its returned projects entries.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is one returned collection per containing GitLab Group object.

Avatar URL

Developer identifier: groups.projects.avatar_urlAvatar URL records URL of the project avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is link at one Group Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Created At

Developer identifier: groups.projects.created_atCreated At records timestamp when the project was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Groups records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the Temporal.DateTime scalar.

Default Branch

Developer identifier: groups.projects.default_branchDefault Branch records default branch name. It is needed to distinguish Groups rows by the exact GitLab-returned default branch value.

Enables: separate Groups rows by the exact GitLab-returned default_branch label when comparing default branch.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Description

Developer identifier: groups.projects.descriptionDescription records project description. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s parent record, owner, status, and update time where returned.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is description text at one Group Project record per row; this is only the content included in the GitLab response for this record.

Forks Count

Developer identifier: groups.projects.forks_countForks Count records number of forks. It is needed to measure the GitLab-reported number of forks at one Group Project record per row.

Enables: measure and compare the GitLab-reported number of forks in forks_count at one Group Project record per row.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is a GitLab-reported count at one Group Project record per row.

HTTP URL To Repo

Developer identifier: groups.projects.http_url_to_repoHTTP URL To Repo records HTTP URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Groups record.

Enables: use http_url_to_repo to locate the configured source, package, or repository when reproducing the same job or repository setup.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: groups.projects.idID records unique numeric identifier for the project. It is needed to distinguish repeated deliveries of the same Groups row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Groups and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Last Activity At

Developer identifier: groups.projects.last_activity_atLast Activity At records timestamp of the last activity on the project. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Groups records by last_activity_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the Temporal.DateTime scalar.

Name

Developer identifier: groups.projects.nameName records human-readable project name. It is needed to compare the returned name for individual Groups rows and select rows with a specific name value.

Enables: locate Groups rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the Identity.Name scalar.

Name With Namespace

Developer identifier: groups.projects.name_with_namespaceName With Namespace records full project name including namespace. It is needed to compare the returned name with namespace for individual Groups rows and select rows with a specific name_with_namespace value.

Enables: locate Groups rows whose returned name with namespace exactly matches name_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row.

Namespace

Developer identifier: groups.projects.namespaceNamespace records namespace the project belongs to. It is needed to preserve the nested namespace relationship or details on the parent Group Project record.

Enables: expand namespace to connect the containing Group Project row to its returned namespace entries.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is one nested object per containing Group Project object when present.

Avatar URL

Developer identifier: groups.projects.namespace.avatar_urlAvatar URL records URL of the namespace avatar. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is link at one Project Namespace record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Full Path

Developer identifier: groups.projects.namespace.full_pathFull Path records full namespace path. It is needed to compare the returned full path for individual Groups rows and select rows with a specific full_path value.

Enables: trace the full path relationship returned in full_path from the Project Namespace row to its named GitLab context.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is interpreted at one Project Namespace record per row.

Developer identifier: groups.projects.namespace.idID records namespace ID. It is needed to refer to the same project namespace across records without relying on display text.

Enables: match id to project namespace references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is an identifier, not a measured quantity.

Kind

Developer identifier: groups.projects.namespace.kindKind records namespace kind (group or user). It is needed to distinguish Groups rows by the exact GitLab-returned kind value.

Enables: separate Groups rows by the exact GitLab-returned kind label when comparing kind.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is interpreted at one Project Namespace record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: groups.projects.namespace.nameName records namespace name. It is needed to compare the returned name for individual Groups rows and select rows with a specific name value.

Enables: locate Groups rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is interpreted at one Project Namespace record per row; the schema uses the Identity.Name scalar.

Parent ID

Developer identifier: groups.projects.namespace.parent_idParent ID records parent namespace ID. It is needed to refer to the same parent across records without relying on display text.

Enables: match parent_id to parent references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is an identifier, not a measured quantity.

Path

Developer identifier: groups.projects.namespace.pathPath records namespace path. It is needed to compare the returned path for individual Groups rows and select rows with a specific path value.

Enables: trace the path relationship returned in path from the Project Namespace row to its named GitLab context.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is interpreted at one Project Namespace record per row; the schema uses the Identity.Slug scalar.

Web URL

Developer identifier: groups.projects.namespace.web_urlWeb URL records URL to the namespace page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the Project Namespace object returned for Groups; it is link at one Project Namespace record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Path

Developer identifier: groups.projects.pathPath records URL-friendly path slug for the project. It is needed to compare the returned path for individual Groups rows and select rows with a specific path value.

Enables: trace the path relationship returned in path from the Group Project row to its named GitLab context.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the schema uses the Identity.Slug scalar.

Path With Namespace

Developer identifier: groups.projects.path_with_namespacePath With Namespace records full path including namespace. It is needed to compare the returned path with namespace for individual Groups rows and select rows with a specific path_with_namespace value.

Enables: locate Groups rows whose returned path with namespace exactly matches path_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row.

Readme URL

Developer identifier: groups.projects.readme_urlReadme URL records URL to the project README file. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by readme_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is link at one Group Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

SSH URL To Repo

Developer identifier: groups.projects.ssh_url_to_repoSSH URL To Repo records SSH URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Groups record.

Enables: use ssh_url_to_repo to locate the configured source, package, or repository when reproducing the same job or repository setup.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is interpreted at one Group Project record per row; the returned link or template does not establish that the current credential can retrieve its target.

Star Count

Developer identifier: groups.projects.star_countStar Count records number of stars. It is needed to measure the GitLab-reported number of stars at one Group Project record per row.

Enables: measure and compare the GitLab-reported number of stars in star_count at one Group Project record per row.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is a GitLab-reported count at one Group Project record per row.

Topics

Developer identifier: groups.projects.topicsTopics records list of topic tags associated with the project. It is needed to preserve the nested topics relationship or details on the parent Group Project record.

Enables: expand topics to connect the containing Group Project row to its returned topics entries.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is one returned collection per containing Group Project object.

Web URL

Developer identifier: groups.projects.web_urlWeb URL records URL to the project page in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the Group Project object returned for Groups; it is link at one Group Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Repository Storage

Developer identifier: groups.repository_storageRepository Storage records name of the repository storage shard. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare repository_storage among Groups records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; the value is a GitLab-returned or configured label at the GitLab Group grain rather than a universal taxonomy.

Request Access Enabled

Developer identifier: groups.request_access_enabledRequest Access Enabled records whether users can request access to the group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Groups rows with the exact request_access_enabled access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Require Two Factor Authentication

Developer identifier: groups.require_two_factor_authenticationRequire Two Factor Authentication records whether two-factor authentication is required for group members. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Groups rows with the exact require_two_factor_authentication access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Runners Token

Developer identifier: groups.runners_tokenRunners Token records token used to register runners for this group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact runners_token access value with the resource, account, or membership represented by the same Groups row.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Shared Projects

Developer identifier: groups.shared_projectsShared Projects records list of projects shared with this group. It is needed to preserve the nested shared projects relationship or details on the parent GitLab Group record.

Enables: expand shared_projects to connect the containing GitLab Group row to its returned shared projects entries.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is one returned collection per containing GitLab Group object.

Shared Runners Minutes Limit

Developer identifier: groups.shared_runners_minutes_limitShared Runners Minutes Limit records CI/CD minutes limit for shared runners. It is needed to measure the reported shared runners minutes limit for one gitlab group record.

Enables: measure and compare shared_runners_minutes_limit per GitLab Group record in minutes.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; its unit or granularity is minutes.

Shared Runners Setting

Developer identifier: groups.shared_runners_settingShared Runners Setting records shared runners availability setting. It is needed to distinguish Groups rows by the exact GitLab-returned shared runners setting value.

Enables: separate Groups rows by the exact GitLab-returned shared_runners_setting label when comparing shared runners setting.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Shared With Groups

Developer identifier: groups.shared_with_groupsShared With Groups records list of groups this group is shared with. It is needed to preserve the explicit GitLab group references attached to this row.

Enables: split the references in shared_with_groups and match each returned group identifier to the corresponding GitLab group record when available.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is one returned collection per containing GitLab Group object.

Expires At

Developer identifier: groups.shared_with_groups.expires_atExpires At records date when the sharing expires. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Groups records by expires_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Shared Group object returned for Groups; it is interpreted at one Shared Group record per row; the schema uses the Temporal.Date scalar.

Group Access Level

Developer identifier: groups.shared_with_groups.group_access_levelGroup Access Level records access level granted to the shared group (e.g., 10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact group_access_level access value with the resource, account, or membership represented by the same Groups row.
Interpretation: GitLab reports this value on the Shared Group object returned for Groups; it is interpreted at one Shared Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Group Full Path

Developer identifier: groups.shared_with_groups.group_full_pathGroup Full Path records full path of the shared group. It is needed to compare the returned group full path for individual Groups rows and select rows with a specific group_full_path value.

Enables: trace the group full path relationship returned in group_full_path from the Shared Group row to its named GitLab context.
Interpretation: GitLab reports this value on the Shared Group object returned for Groups; it is interpreted at one Shared Group record per row.

Group ID

Developer identifier: groups.shared_with_groups.group_idGroup ID records ID of the shared group. It is needed to distinguish repeated deliveries of the same Groups row using the declared ingestion key.

Enables: use group_id as the declared ingestion deduplication key for Groups and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the Shared Group object returned for Groups; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Group Name

Developer identifier: groups.shared_with_groups.group_nameGroup Name records name of the shared group. It is needed to compare the returned group name for individual Groups rows and select rows with a specific group_name value.

Enables: locate Groups rows whose returned group name exactly matches group_name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the Shared Group object returned for Groups; it is interpreted at one Shared Group record per row.

Statistics

Developer identifier: groups.statisticsStatistics records storage and usage statistics for the group. It is needed to preserve the nested statistics relationship or details on the parent GitLab Group record.

Enables: expand statistics to connect the containing GitLab Group row to its returned statistics entries.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is one nested object per containing GitLab Group object when present.

Job Artifacts Size

Developer identifier: groups.statistics.job_artifacts_sizeJob Artifacts Size records total job artifacts size in bytes. It is needed to measure the reported job artifacts size for one group statistics record.

Enables: measure and compare job_artifacts_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Lfs Objects Size

Developer identifier: groups.statistics.lfs_objects_sizeLfs Objects Size records total LFS objects size in bytes. It is needed to measure the reported lfs objects size for one group statistics record.

Enables: measure and compare lfs_objects_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Packages Size

Developer identifier: groups.statistics.packages_sizePackages Size records total packages size in bytes. It is needed to measure the reported packages size for one group statistics record.

Enables: measure and compare packages_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Pipeline Artifacts Size

Developer identifier: groups.statistics.pipeline_artifacts_sizePipeline Artifacts Size records total pipeline artifacts size in bytes. It is needed to measure the reported pipeline artifacts size for one group statistics record.

Enables: measure and compare pipeline_artifacts_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Repository Size

Developer identifier: groups.statistics.repository_sizeRepository Size records total repository size in bytes. It is needed to measure the reported repository size for one group statistics record.

Enables: measure and compare repository_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Snippets Size

Developer identifier: groups.statistics.snippets_sizeSnippets Size records total snippets size in bytes. It is needed to measure the reported snippets size for one group statistics record.

Enables: measure and compare snippets_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Storage Size

Developer identifier: groups.statistics.storage_sizeStorage Size records total storage size in bytes. It is needed to measure the reported storage size for one group statistics record.

Enables: measure and compare storage_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Uploads Size

Developer identifier: groups.statistics.uploads_sizeUploads Size records total uploads size in bytes. It is needed to measure the reported uploads size for one group statistics record.

Enables: measure and compare uploads_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Wiki Size

Developer identifier: groups.statistics.wiki_sizeWiki Size records total wiki size in bytes. It is needed to measure the reported wiki size for one group statistics record.

Enables: measure and compare wiki_size per Group Statistics record in bytes.
Interpretation: GitLab reports this value on the Group Statistics object returned for Groups; its unit or granularity is bytes.

Subgroup Creation Level

Developer identifier: groups.subgroup_creation_levelSubgroup Creation Level records who can create subgroups in this group. It is needed to distinguish Groups rows by the exact GitLab-returned subgroup creation level value.

Enables: separate Groups rows by the exact GitLab-returned subgroup_creation_level label when comparing subgroup creation level.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Two Factor Grace Period

Developer identifier: groups.two_factor_grace_periodTwo Factor Grace Period records grace period in hours before 2FA enforcement. It is needed to measure the reported two factor grace period for one gitlab group record.

Enables: measure and compare two_factor_grace_period per GitLab Group record in hours.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; its unit or granularity is hours.

Visibility

Developer identifier: groups.visibilityVisibility records group visibility level (private, internal, or public). It is needed to distinguish Groups rows by the exact GitLab-returned visibility value.

Enables: separate Groups rows by the exact GitLab-returned visibility label when comparing visibility.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Web URL

Developer identifier: groups.web_urlWeb URL records URL to the group page in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Groups record as provenance.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is link at one GitLab Group record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Wiki Access Level

Developer identifier: groups.wiki_access_levelWiki Access Level records access level for the group wiki. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Groups rows with the exact wiki_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Group object returned for Groups; it is interpreted at one GitLab Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Issues

Developer identifier: issuesIssues covers project issues.

Enables: follow each returned issue from its repository or project and issue number through author, assignee, state, and update time.
Scope: Project issues; the connector reads /api/v4/projects/{id}/issues as a changelog stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Links

Developer identifier: issues._linksLinks records related resource links for the issue. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by _links while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is link at one GitLab Issue record per row; the returned link or template does not establish that the current credential can retrieve its target.

Award Emoji

Developer identifier: issues._links.award_emojiAward Emoji records API URL for award emoji on this issue. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by award_emoji while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue Links object returned for Issues; it is link at one GitLab Issue Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Closed As Duplicate Of

Developer identifier: issues._links.closed_as_duplicate_ofClosed As Duplicate Of records API URL of the issue this was closed as a duplicate of. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by closed_as_duplicate_of while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue Links object returned for Issues; it is link at one GitLab Issue Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Notes

Developer identifier: issues._links.notesNotes records API URL for notes on this issue. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by notes while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue Links object returned for Issues; it is link at one GitLab Issue Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Project

Developer identifier: issues._links.projectProject records API URL for the project this issue belongs to. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by project while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue Links object returned for Issues; it is link at one GitLab Issue Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Self

Developer identifier: issues._links.selfSelf records API URL for this issue. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by self while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue Links object returned for Issues; it is link at one GitLab Issue Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Assignees

Developer identifier: issues.assigneesAssignees records array of users assigned to the issue. It is needed to preserve the nested assignees relationship or details on the parent GitLab Issue record.

Enables: expand assignees to connect the containing GitLab Issue row to its returned assignees entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one returned collection per containing GitLab Issue object.

Avatar URL

Developer identifier: issues.assignees.avatar_urlAvatar URL records URL to the user’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is link at one GitLab User Reference record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: issues.assignees.idID records unique numeric user ID. It is needed to distinguish repeated deliveries of the same Issues row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Issues and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Locked

Developer identifier: issues.assignees.lockedLocked records whether the user account is locked. It is needed to distinguish Issues rows by the exact GitLab-returned locked value.

Enables: select Issues rows where locked is true or false when comparing the condition described by Locked.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: issues.assignees.nameName records display name of the user. It is needed to attribute this Issues row to the returned person, account, or organization reference.

Enables: attribute the Issues row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row; the schema uses the Identity.Name scalar.

Public Email

Developer identifier: issues.assignees.public_emailPublic Email records public email address of the user, enriched by the ingestion service via the GitLab Users API. Absent when the user has no public email set or when the enrichment call is suppressed (e.g. rate-limited backfills). Silver layers must treat this field as optional. It is needed to distinguish Issues rows by the exact GitLab-returned public email value.

Enables: separate Issues rows by the exact GitLab-returned public_email label when comparing public email.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row; the schema uses the Contact.Email scalar; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: issues.assignees.stateState records user account state (e.g., active, blocked). It is needed to distinguish Issues rows by the exact GitLab-returned state value.

Enables: separate Issues rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: issues.assignees.usernameUser Name records GitLab username. It is needed to attribute this Issues row to the returned person, account, or organization reference.

Enables: attribute the Issues row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is interpreted at one GitLab User Reference record per row.

Web URL

Developer identifier: issues.assignees.web_urlWeb URL records URL to the user’s GitLab profile. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab User Reference object returned for Issues; it is link at one GitLab User Reference record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Author

Developer identifier: issues.authorAuthor records user who created the issue. It is needed to preserve the nested author relationship or details on the parent GitLab Issue record.

Enables: expand author to connect the containing GitLab Issue row to its returned author entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Blocking Issues Count

Developer identifier: issues.blocking_issues_countBlocking Issues Count records number of issues this issue is blocking. It is needed to measure the GitLab-reported number of issues this issue is blocking at one GitLab Issue record per row.

Enables: measure and compare the GitLab-reported number of issues this issue is blocking in blocking_issues_count at one GitLab Issue record per row.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.

Closed At

Developer identifier: issues.closed_atClosed At records timestamp when the issue was closed. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by closed_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; the schema uses the Temporal.DateTime scalar.

Closed By

Developer identifier: issues.closed_byClosed By records user who closed the issue. It is needed to preserve the nested closed by relationship or details on the parent GitLab Issue record.

Enables: expand closed_by to connect the containing GitLab Issue row to its returned closed by entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Confidential

Developer identifier: issues.confidentialConfidential records whether the issue is confidential. It is needed to distinguish Issues rows by the exact GitLab-returned confidential value.

Enables: select Issues rows where confidential is true or false when comparing the condition described by Confidential.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Created At

Developer identifier: issues.created_atCreated At records timestamp when the issue was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; the schema uses the Temporal.DateTime scalar.

Description

Developer identifier: issues.descriptionDescription records full issue description in Markdown. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is description text at one GitLab Issue record per row; the schema uses the Text.Markdown scalar; this is only the content included in the GitLab response for this record.

Discussion Locked

Developer identifier: issues.discussion_lockedDiscussion Locked records whether discussion on the issue is locked. It is needed to distinguish Issues rows by the exact GitLab-returned discussion locked value.

Enables: select Issues rows where discussion_locked is true or false when comparing the condition described by Discussion Locked.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Downvotes

Developer identifier: issues.downvotesDownvotes records number of downvotes (thumbs down) on the issue. It is needed to measure the GitLab-reported number of downvotes (thumbs down) on the issue at one GitLab Issue record per row.

Enables: measure and compare the GitLab-reported number of downvotes (thumbs down) on the issue in downvotes at one GitLab Issue record per row.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.

Due Date

Developer identifier: issues.due_dateDue Date records due date for the issue in YYYY-MM-DD format. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by due_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; the schema uses the Temporal.Date scalar.

Epic

Developer identifier: issues.epicEpic records epic this issue belongs to. It is needed to preserve the nested epic relationship or details on the parent GitLab Issue record.

Enables: expand epic to connect the containing GitLab Issue row to its returned epic entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Group ID

Developer identifier: issues.epic.group_idGroup ID records ID of the group this epic belongs to. It is needed to refer to the same group across records without relying on display text.

Enables: match group_id to group references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is an identifier, not a measured quantity.

Developer identifier: issues.epic.idID records unique global numeric identifier for the epic. It is needed to refer to the same epic reference across records without relying on display text.

Enables: match id to epic reference references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is an identifier, not a measured quantity.

Iid

Developer identifier: issues.epic.iidIid records group-scoped epic number. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is an identifier, not a measured quantity.

Title

Developer identifier: issues.epic.titleTitle records epic title. It is needed to inspect the exact title text included with this record.

Enables: inspect the title text returned in title and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is title text at one GitLab Epic Reference record per row; this is only the content included in the GitLab response for this record.

URL

Developer identifier: issues.epic.urlURL records URL to view the epic in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by url while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Epic Reference object returned for Issues; it is link at one GitLab Epic Reference record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Epic Iid

Developer identifier: issues.epic_iidEpic Iid records IID of the epic this issue belongs to. It is needed to refer to the same epic iid across records without relying on display text.

Enables: match epic_iid to epic iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is an identifier, not a measured quantity.

Has Tasks

Developer identifier: issues.has_tasksHas Tasks records whether the issue description contains task list items. It is needed to distinguish Issues rows by the exact GitLab-returned has tasks value.

Enables: select Issues rows where has_tasks is true or false when comparing the condition described by Has Tasks.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Health Status

Developer identifier: issues.health_statusHealth Status records health status of the issue (on_track, needs_attention, at_risk). It is needed to distinguish Issues rows by the exact GitLab-returned health status value.

Enables: separate Issues rows by the exact GitLab-returned health_status label when comparing health status.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Developer identifier: issues.idID records unique global numeric identifier for the issue. It is needed to distinguish repeated deliveries of the same Issues row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Issues and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Iid

Developer identifier: issues.iidIid records project-scoped issue number. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is an identifier, not a measured quantity.

Imported

Developer identifier: issues.importedImported records whether this issue was imported from an external source. It is needed to distinguish Issues rows by the exact GitLab-returned imported value.

Enables: select Issues rows where imported is true or false when comparing the condition described by Imported.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Imported From

Developer identifier: issues.imported_fromImported From records the source from which this issue was imported, if applicable. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare imported_from among Issues records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; the value is a GitLab-returned or configured label at the GitLab Issue grain rather than a universal taxonomy.

Issue Type

Developer identifier: issues.issue_typeIssue Type records type classification of the issue. It is needed to distinguish Issues rows by the exact GitLab-returned issue type value.

Enables: separate Issues rows by the exact GitLab-returned issue_type label when comparing issue type.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Iteration

Developer identifier: issues.iterationIteration records iteration this issue is assigned to. It is needed to preserve the nested iteration relationship or details on the parent GitLab Issue record.

Enables: expand iteration to connect the containing GitLab Issue row to its returned iteration entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Created At

Developer identifier: issues.iteration.created_atCreated At records timestamp when the iteration was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is interpreted at one GitLab Iteration record per row; the schema uses the Temporal.DateTime scalar.

Description

Developer identifier: issues.iteration.descriptionDescription records iteration description. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is description text at one GitLab Iteration record per row; this is only the content included in the GitLab response for this record.

Due Date

Developer identifier: issues.iteration.due_dateDue Date records due date of the iteration. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by due_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is interpreted at one GitLab Iteration record per row; the schema uses the Temporal.Date scalar.

Group ID

Developer identifier: issues.iteration.group_idGroup ID records ID of the group this iteration belongs to. It is needed to refer to the same group across records without relying on display text.

Enables: match group_id to group references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is an identifier, not a measured quantity.

Developer identifier: issues.iteration.idID records unique global numeric identifier for the iteration. It is needed to refer to the same iteration across records without relying on display text.

Enables: match id to iteration references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is an identifier, not a measured quantity.

Iid

Developer identifier: issues.iteration.iidIid records group-scoped iteration number. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is an identifier, not a measured quantity.

Sequence

Developer identifier: issues.iteration.sequenceSequence records sequence number of the iteration. It is needed to measure the GitLab-reported number of sequence at one GitLab Iteration record per row.

Enables: measure and compare the GitLab-reported number of sequence in sequence at one GitLab Iteration record per row.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is a GitLab-reported count at one GitLab Iteration record per row.

Start Date

Developer identifier: issues.iteration.start_dateStart Date records start date of the iteration. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by start_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is interpreted at one GitLab Iteration record per row; the schema uses the Temporal.Date scalar.

State

Developer identifier: issues.iteration.stateState records iteration state as numeric value. It is needed to distinguish Issues rows by the exact GitLab-returned state value.

Enables: separate Issues rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is interpreted at one GitLab Iteration record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Title

Developer identifier: issues.iteration.titleTitle records iteration title. It is needed to inspect the exact title text included with this record.

Enables: inspect the title text returned in title and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is title text at one GitLab Iteration record per row; this is only the content included in the GitLab response for this record.

Updated At

Developer identifier: issues.iteration.updated_atUpdated At records timestamp when the iteration was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is interpreted at one GitLab Iteration record per row; the schema uses the Temporal.DateTime scalar.

Web URL

Developer identifier: issues.iteration.web_urlWeb URL records URL to view the iteration in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Iteration object returned for Issues; it is link at one GitLab Iteration record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Labels

Developer identifier: issues.labelsLabels records array of label names applied to the issue. It is needed to preserve the nested labels relationship or details on the parent GitLab Issue record.

Enables: expand labels to connect the containing GitLab Issue row to its returned labels entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one returned collection per containing GitLab Issue object.

Merge Requests Count

Developer identifier: issues.merge_requests_countMerge Requests Count records number of merge requests related to this issue. It is needed to measure the GitLab-reported number of merge requests related to this issue at one GitLab Issue record per row.

Enables: measure and compare the GitLab-reported number of merge requests related to this issue in merge_requests_count at one GitLab Issue record per row.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.

Milestone

Developer identifier: issues.milestoneMilestone records milestone the issue is assigned to. It is needed to preserve the nested milestone relationship or details on the parent GitLab Issue record.

Enables: expand milestone to connect the containing GitLab Issue row to its returned milestone entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Created At

Developer identifier: issues.milestone.created_atCreated At records timestamp when the milestone was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is interpreted at one GitLab Milestone record per row; the schema uses the Temporal.DateTime scalar.

Description

Developer identifier: issues.milestone.descriptionDescription records milestone description. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is description text at one GitLab Milestone record per row; this is only the content included in the GitLab response for this record.

Due Date

Developer identifier: issues.milestone.due_dateDue Date records due date for the milestone. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by due_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is interpreted at one GitLab Milestone record per row; the schema uses the Temporal.Date scalar.

Expired

Developer identifier: issues.milestone.expiredExpired records whether the milestone is past its due date. It is needed to distinguish Issues rows by the exact GitLab-returned expired value.

Enables: select Issues rows where expired is true or false when comparing the condition described by Expired.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is interpreted at one GitLab Milestone record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Group ID

Developer identifier: issues.milestone.group_idGroup ID records ID of the group this milestone belongs to (for group milestones). It is needed to refer to the same group across records without relying on display text.

Enables: match group_id to group references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is an identifier, not a measured quantity.

Developer identifier: issues.milestone.idID records unique global numeric identifier for the milestone. It is needed to refer to the same milestone across records without relying on display text.

Enables: match id to milestone references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is an identifier, not a measured quantity.

Iid

Developer identifier: issues.milestone.iidIid records project-scoped milestone number. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is an identifier, not a measured quantity.

Project ID

Developer identifier: issues.milestone.project_idProject ID records ID of the project this milestone belongs to. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is an identifier, not a measured quantity.

Start Date

Developer identifier: issues.milestone.start_dateStart Date records start date for the milestone. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by start_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is interpreted at one GitLab Milestone record per row; the schema uses the Temporal.Date scalar.

State

Developer identifier: issues.milestone.stateState records milestone state (active or closed). It is needed to distinguish Issues rows by the exact GitLab-returned state value.

Enables: separate Issues rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is interpreted at one GitLab Milestone record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Title

Developer identifier: issues.milestone.titleTitle records milestone title. It is needed to inspect the exact title text included with this record.

Enables: inspect the title text returned in title and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is title text at one GitLab Milestone record per row; this is only the content included in the GitLab response for this record.

Updated At

Developer identifier: issues.milestone.updated_atUpdated At records timestamp when the milestone was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is interpreted at one GitLab Milestone record per row; the schema uses the Temporal.DateTime scalar.

Web URL

Developer identifier: issues.milestone.web_urlWeb URL records URL to view the milestone in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Milestone object returned for Issues; it is link at one GitLab Milestone record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Moved To ID

Developer identifier: issues.moved_to_idMoved To ID records ID of the issue this was moved to, if moved. It is needed to refer to the same moved to across records without relying on display text.

Enables: match moved_to_id to moved to references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is an identifier, not a measured quantity.

Project ID

Developer identifier: issues.project_idProject ID records ID of the project this issue belongs to. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is an identifier, not a measured quantity.

References

Developer identifier: issues.referencesReferences records short and full reference strings for the issue. It is needed to preserve the nested references relationship or details on the parent GitLab Issue record.

Enables: expand references to connect the containing GitLab Issue row to its returned references entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Full

Developer identifier: issues.references.fullFull records full reference including project path (e.g., group/project#123). It is needed to compare the returned full for individual Issues rows and select rows with a specific full value.

Enables: trace the full relationship returned in full from the GitLab References row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab References object returned for Issues; it is interpreted at one GitLab References record per row.

Relative

Developer identifier: issues.references.relativeRelative records relative reference within the project. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match relative to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the GitLab References object returned for Issues; it is interpreted at one GitLab References record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Short

Developer identifier: issues.references.shortShort records short reference (e.g., #123). It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match short to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the GitLab References object returned for Issues; it is interpreted at one GitLab References record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Service Desk Reply To

Developer identifier: issues.service_desk_reply_toService Desk Reply To records email address for service desk replies. It is needed to attribute this Issues row to the returned person, account, or organization reference.

Enables: attribute the Issues row to the returned person or account and match the exact service_desk_reply_to value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; the schema uses the Contact.Email scalar.

Severity

Developer identifier: issues.severitySeverity records severity level for incident-type issues. It is needed to distinguish Issues rows by the exact GitLab-returned severity value.

Enables: separate Issues rows by the exact GitLab-returned severity label when comparing severity.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: issues.stateState records issue state (opened or closed). It is needed to distinguish Issues rows by the exact GitLab-returned state value.

Enables: separate Issues rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Task Completion Status

Developer identifier: issues.task_completion_statusTask Completion Status records completion status of tasks within the issue description. It is needed to preserve the nested task completion status relationship or details on the parent GitLab Issue record.

Enables: expand task_completion_status to connect the containing GitLab Issue row to its returned task completion status entries.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Completed Count

Developer identifier: issues.task_completion_status.completed_countCompleted Count records number of completed tasks. It is needed to measure the GitLab-reported number of completed tasks at one GitLab Task Completion Status record per row.

Enables: measure and compare the GitLab-reported number of completed tasks in completed_count at one GitLab Task Completion Status record per row.
Interpretation: GitLab reports this value on the GitLab Task Completion Status object returned for Issues; it is a GitLab-reported count at one GitLab Task Completion Status record per row.

Count

Developer identifier: issues.task_completion_status.countCount records total number of tasks. It is needed to measure the GitLab-reported number of tasks at one GitLab Task Completion Status record per row.

Enables: measure and compare the GitLab-reported number of tasks in count at one GitLab Task Completion Status record per row.
Interpretation: GitLab reports this value on the GitLab Task Completion Status object returned for Issues; it is a GitLab-reported count at one GitLab Task Completion Status record per row.

Task Status

Developer identifier: issues.task_statusTask Status records human-readable task completion status string. It is needed to distinguish Issues rows by the exact GitLab-returned task status value.

Enables: separate Issues rows by the exact GitLab-returned task_status label when comparing task status.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Time Stats

Developer identifier: issues.time_statsTime Stats records time tracking statistics for the issue. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by time_stats, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is one nested object per containing GitLab Issue object when present.

Human Time Estimate

Developer identifier: issues.time_stats.human_time_estimateHuman Time Estimate records human-readable time estimate string. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by human_time_estimate, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Time Stats object returned for Issues; it is interpreted at one GitLab Time Stats record per row.

Human Total Time Spent

Developer identifier: issues.time_stats.human_total_time_spentHuman Total Time Spent records human-readable total time spent string. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by human_total_time_spent, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Time Stats object returned for Issues; it is interpreted at one GitLab Time Stats record per row.

Time Estimate

Developer identifier: issues.time_stats.time_estimateTime Estimate records estimated time in seconds. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by time_estimate, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Time Stats object returned for Issues; its unit or granularity is seconds.

Total Time Spent

Developer identifier: issues.time_stats.total_time_spentTotal Time Spent records total time spent in seconds. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by total_time_spent, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Time Stats object returned for Issues; its unit or granularity is seconds.

Title

Developer identifier: issues.titleTitle records issue title. It is needed to inspect the exact title text included with this record.

Enables: inspect the title text returned in title and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is title text at one GitLab Issue record per row; this is only the content included in the GitLab response for this record.

Type

Developer identifier: issues.typeType records issue type (e.g., issue, incident, test_case, task). It is needed to distinguish Issues rows by the exact GitLab-returned type value.

Enables: separate Issues rows by the exact GitLab-returned type label when comparing type.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Updated At

Developer identifier: issues.updated_atUpdated At records timestamp when the issue was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Issues records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Upvotes

Developer identifier: issues.upvotesUpvotes records number of upvotes (thumbs up) on the issue. It is needed to measure the GitLab-reported number of upvotes (thumbs up) on the issue at one GitLab Issue record per row.

Enables: measure and compare the GitLab-reported number of upvotes (thumbs up) on the issue in upvotes at one GitLab Issue record per row.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.

User Notes Count

Developer identifier: issues.user_notes_countUser Notes Count records number of user-created notes (comments) on the issue. It is needed to measure the GitLab-reported number of user-created notes (comments) on the issue at one GitLab Issue record per row.

Enables: measure and compare the GitLab-reported number of user-created notes (comments) on the issue in user_notes_count at one GitLab Issue record per row.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is a GitLab-reported count at one GitLab Issue record per row.

Web URL

Developer identifier: issues.web_urlWeb URL records URL to view the issue in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Issues record as provenance.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is link at one GitLab Issue record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Weight

Developer identifier: issues.weightWeight records issue weight (effort estimate). It is needed to compare the numeric weight reported for one GitLab Issue record without assuming an unstated unit.

Enables: compare the numeric weight value per GitLab Issue record without assigning a unit not declared by the schema description.
Interpretation: GitLab reports this value on the GitLab Issue object returned for Issues; it is interpreted at one GitLab Issue record per row.

Merge Request Notes

Developer identifier: merge_request_notesMerge Request Notes covers notes (comments) on merge requests.

Enables: attribute each returned review comment or note to its work item, author, file or diff position, and time where those fields are present.
Scope: Notes (comments) on merge requests; the connector reads /api/v4/projects/{project_id}/merge_requests/{iid}/notes as a changelog stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Attachment

Developer identifier: merge_request_notes.attachmentAttachment records the filename of an attachment on the note, if any. It is needed to inspect the exact attachment filename returned for this GitLab Merge Request Note record.

Enables: attribute the attachment filename in attachment to the containing Merge Request Notes identifier, owner or author, status, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; this is only the attachment filename included in the GitLab response for this record.

Author

Developer identifier: merge_request_notes.authorAuthor records the user who authored the note. It is needed to preserve the nested author relationship or details on the parent GitLab Merge Request Note record.

Enables: expand author to connect the containing GitLab Merge Request Note row to its returned author entries.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.

Avatar URL

Developer identifier: merge_request_notes.author.avatar_urlAvatar URL records URL to the user’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Merge Request Notes record as provenance.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is link at one Note Author record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: merge_request_notes.author.emailEmail records the email address of the user (may be empty if private). It is needed to attribute this Merge Request Notes row to the returned person, account, or organization reference.

Enables: attribute the Merge Request Notes row to the returned person or account and match the exact email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; the schema uses the Contact.Email scalar.

Developer identifier: merge_request_notes.author.idID records unique identifier of the user. It is needed to refer to the same note author across records without relying on display text.

Enables: match id to note author references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Locked

Developer identifier: merge_request_notes.author.lockedLocked records whether the user account is locked. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned locked value.

Enables: select Merge Request Notes rows where locked is true or false when comparing the condition described by Locked.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: merge_request_notes.author.nameName records the display name of the user. It is needed to attribute this Merge Request Notes row to the returned person, account, or organization reference.

Enables: attribute the Merge Request Notes row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; the schema uses the Identity.Name scalar.

Public Email

Developer identifier: merge_request_notes.author.public_emailPublic Email records public email address, enriched by the ingestion service via the GitLab Users API. Absent when the user has no public email set or when enrichment is suppressed (e.g. rate-limited backfills). Silver layers must treat this field as optional. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned public email value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned public_email label when comparing public email.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; the schema uses the Contact.Email scalar; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: merge_request_notes.author.stateState records the current state of the user account. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned state value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: merge_request_notes.author.usernameUser Name records the username/handle of the user. It is needed to attribute this Merge Request Notes row to the returned person, account, or organization reference.

Enables: attribute the Merge Request Notes row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is interpreted at one Note Author record per row.

Web URL

Developer identifier: merge_request_notes.author.web_urlWeb URL records URL to the user’s GitLab profile page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Merge Request Notes record as provenance.
Interpretation: GitLab reports this value on the Note Author object returned for Merge Request Notes; it is link at one Note Author record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Body

Developer identifier: merge_request_notes.bodyBody records the text content of the note/comment. It is needed to inspect the exact comment body included with this record.

Enables: inspect the comment body returned in body and attribute it to the same record’s repository or project, revision, file path, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is comment body at one GitLab Merge Request Note record per row; this is only the content included in the GitLab response for this record.

Change Position

Developer identifier: merge_request_notes.change_positionChange Position records updated position information if the diff has changed since the note was created. It is needed to preserve the nested change position relationship or details on the parent GitLab Merge Request Note record.

Enables: expand change_position to connect the containing GitLab Merge Request Note row to its returned change position entries.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.

Base Sha

Developer identifier: merge_request_notes.change_position.base_shaBase Sha records the base commit SHA of the diff. It is needed to refer to the same base across records without relying on display text.

Enables: match base_sha to base references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Head Sha

Developer identifier: merge_request_notes.change_position.head_shaHead Sha records the head commit SHA of the diff. It is needed to refer to the same head across records without relying on display text.

Enables: match head_sha to head references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Height

Developer identifier: merge_request_notes.change_position.heightHeight records height of the image, for image diff notes. It is needed to compare the numeric height reported for one Diff Position record without assuming an unstated unit.

Enables: compare the numeric height value per Diff Position record without assigning a unit not declared by the schema description.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.

Line Range

Developer identifier: merge_request_notes.change_position.line_rangeLine Range records the range of lines this note covers, for multi-line diff notes. It is needed to preserve the nested line range relationship or details on the parent Diff Position record.

Enables: expand line_range to connect the containing Diff Position row to its returned line range entries.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is one nested object per containing Diff Position object when present.

End

Developer identifier: merge_request_notes.change_position.line_range.endEnd records the end position of the line range. It is needed to preserve the nested end relationship or details on the parent Line Range record.

Enables: expand end to connect the containing Line Range row to its returned end entries.
Interpretation: GitLab reports this value on the Line Range object returned for Merge Request Notes; it is one nested object per containing Line Range object when present.

Line Code

Developer identifier: merge_request_notes.change_position.line_range.end.line_codeLine Code records the internal line code identifier. It is needed to refer to the same line code across records without relying on display text.

Enables: match line_code to line code references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Line Position object returned for Merge Request Notes; it is an identifier, not a measured quantity; classification values are GitLab-returned labels rather than a universal taxonomy.

New Line

Developer identifier: merge_request_notes.change_position.line_range.end.new_lineNew Line records the line number in the new version. It is needed to compare the exact new line configuration returned for this Line Position record.

Enables: compare the exact new_line configuration returned for each Line Position record and select records with the configuration under review.
Interpretation: GitLab reports this value on the Line Position object returned for Merge Request Notes; it is interpreted at one Line Position record per row.

Old Line

Developer identifier: merge_request_notes.change_position.line_range.end.old_lineOld Line records the line number in the old version. It is needed to compare the exact old line configuration returned for this Line Position record.

Enables: compare the exact old_line configuration returned for each Line Position record and select records with the configuration under review.
Interpretation: GitLab reports this value on the Line Position object returned for Merge Request Notes; it is interpreted at one Line Position record per row.

Type

Developer identifier: merge_request_notes.change_position.line_range.end.typeType records the type of line (new or old). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned type value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned type label when comparing type.
Interpretation: GitLab reports this value on the Line Position object returned for Merge Request Notes; it is interpreted at one Line Position record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Start

Developer identifier: merge_request_notes.change_position.line_range.startStart records the start position of the line range. It is needed to preserve the nested start relationship or details on the parent Line Range record.

Enables: expand start to connect the containing Line Range row to its returned start entries.
Interpretation: GitLab reports this value on the Line Range object returned for Merge Request Notes; it is one nested object per containing Line Range object when present.

New Line

Developer identifier: merge_request_notes.change_position.new_lineNew Line records the line number in the new version of the file. It is needed to compare the exact new line configuration returned for this Diff Position record.

Enables: compare the exact new_line configuration returned for each Diff Position record and select records with the configuration under review.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.

New Path

Developer identifier: merge_request_notes.change_position.new_pathNew Path records the file path in the new version of the diff. It is needed to compare the exact new path configuration returned for this Diff Position record.

Enables: compare the exact new_path configuration returned for each Diff Position record and select records with the configuration under review.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.

Old Line

Developer identifier: merge_request_notes.change_position.old_lineOld Line records the line number in the old version of the file. It is needed to compare the exact old line configuration returned for this Diff Position record.

Enables: compare the exact old_line configuration returned for each Diff Position record and select records with the configuration under review.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.

Old Path

Developer identifier: merge_request_notes.change_position.old_pathOld Path records the file path in the old version of the diff. It is needed to compare the exact old path configuration returned for this Diff Position record.

Enables: compare the exact old_path configuration returned for each Diff Position record and select records with the configuration under review.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.

Position Type

Developer identifier: merge_request_notes.change_position.position_typePosition Type records the type of position (e.g., text, image, file). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned position type value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned position_type label when comparing position type.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Start Sha

Developer identifier: merge_request_notes.change_position.start_shaStart Sha records the start commit SHA of the diff. It is needed to refer to the same start across records without relying on display text.

Enables: match start_sha to start references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Width

Developer identifier: merge_request_notes.change_position.widthWidth records width of the image, for image diff notes. It is needed to compare the numeric width reported for one Diff Position record without assuming an unstated unit.

Enables: compare the numeric width value per Diff Position record without assigning a unit not declared by the schema description.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; it is interpreted at one Diff Position record per row.

X Coordinate

Developer identifier: merge_request_notes.change_position.xX Coordinate records x coordinate on the image, for image diff notes. It is needed to measure the reported x coordinate for one diff position record.

Enables: measure and compare x per Diff Position record in provider-reported geographic coordinates.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; its unit or granularity is provider-reported geographic coordinates.

Y Coordinate

Developer identifier: merge_request_notes.change_position.yY Coordinate records y coordinate on the image, for image diff notes. It is needed to measure the reported y coordinate for one diff position record.

Enables: measure and compare y per Diff Position record in provider-reported geographic coordinates.
Interpretation: GitLab reports this value on the Diff Position object returned for Merge Request Notes; its unit or granularity is provider-reported geographic coordinates.

Commands Changes

Developer identifier: merge_request_notes.commands_changesCommands Changes records quick action commands that were applied when the note was created. It is needed to preserve the exact GitLab configuration or execution metadata attached to this GitLab Merge Request Note record.

Enables: inspect the keys in commands_changes when reproducing or investigating this record’s configuration, parameters, or execution context.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the schema uses the Generic.JSON scalar; metadata keys and availability follow the GitLab response and can vary by resource type or configuration.

Commit ID

Developer identifier: merge_request_notes.commit_idCommit ID records the commit SHA this diff note references, if applicable. It is needed to refer to the same commit across records without relying on display text.

Enables: match commit_id to commit references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Confidential

Developer identifier: merge_request_notes.confidentialConfidential records whether this note is confidential (visible only to project members with Reporter role or above). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Merge Request Notes rows with the exact confidential access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Created At

Developer identifier: merge_request_notes.created_atCreated At records when the note was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Request Notes records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the schema uses the Temporal.DateTime scalar.

Developer identifier: merge_request_notes.idID records unique identifier of the note. It is needed to distinguish repeated deliveries of the same Merge Request Notes row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Merge Request Notes and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Imported

Developer identifier: merge_request_notes.importedImported records whether this note was imported from an external source. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned imported value.

Enables: select Merge Request Notes rows where imported is true or false when comparing the condition described by Imported.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Imported From

Developer identifier: merge_request_notes.imported_fromImported From records the source from which this note was imported, if applicable. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare imported_from among Merge Request Notes records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the value is a GitLab-returned or configured label at the GitLab Merge Request Note grain rather than a universal taxonomy.

Internal

Developer identifier: merge_request_notes.internalInternal records whether this note is internal (same as confidential in newer API versions). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned internal value.

Enables: select Merge Request Notes rows where internal is true or false when comparing the condition described by Internal.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Line Type

Developer identifier: merge_request_notes.line_typeLine Type records for diff notes, whether the comment is on an old or new line. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned line type value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned line_type label when comparing line type.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Noteable ID

Developer identifier: merge_request_notes.noteable_idNoteable ID records ID of the merge request this note belongs to. It is needed to refer to the same noteable across records without relying on display text.

Enables: match noteable_id to noteable references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Noteable Iid

Developer identifier: merge_request_notes.noteable_iidNoteable Iid records internal ID (IID) of the merge request within the project. It is needed to refer to the same noteable iid across records without relying on display text.

Enables: match noteable_iid to noteable iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is an identifier, not a measured quantity.

Noteable Type

Developer identifier: merge_request_notes.noteable_typeNoteable Type records the type of the parent noteable object (e.g., MergeRequest). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned noteable type value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned noteable_type label when comparing noteable type.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Position

Developer identifier: merge_request_notes.positionPosition records position information for diff notes, indicating the file and line location. It is needed to preserve the nested position relationship or details on the parent GitLab Merge Request Note record.

Enables: expand position to connect the containing GitLab Merge Request Note row to its returned position entries.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.

Project ID

Developer identifier: merge_request_notes.project_idProject ID records ID of the project containing the merge request. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Resolvable

Developer identifier: merge_request_notes.resolvableResolvable records whether this note is a resolvable discussion thread. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned resolvable value.

Enables: select Merge Request Notes rows where resolvable is true or false when comparing the condition described by Resolvable.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Resolved

Developer identifier: merge_request_notes.resolvedResolved records whether this resolvable note has been resolved. It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned resolved value.

Enables: select Merge Request Notes rows where resolved is true or false when comparing the condition described by Resolved.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Resolved At

Developer identifier: merge_request_notes.resolved_atResolved At records timestamp when the note was resolved. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Request Notes records by resolved_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the schema uses the Temporal.DateTime scalar.

Resolved By

Developer identifier: merge_request_notes.resolved_byResolved By records the user who resolved this note, if resolved. It is needed to preserve the nested resolved by relationship or details on the parent GitLab Merge Request Note record.

Enables: expand resolved_by to connect the containing GitLab Merge Request Note row to its returned resolved by entries.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is one nested object per containing GitLab Merge Request Note object when present.

Suggestions

Developer identifier: merge_request_notes.suggestionsSuggestions records inline code suggestions attached to a diff note, enriched by the ingestion service via a follow-up call to the GitLab Notes Suggestions API. Absent on non-diff notes or when enrichment is suppressed. Silver layers must treat this field as optional and JSON-encoded. It is needed to compare the exact suggestions configuration returned for this GitLab Merge Request Note record.

Enables: compare the exact suggestions configuration returned for each GitLab Merge Request Note record and select records with the configuration under review.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the schema uses the Generic.JSON scalar.

System

Developer identifier: merge_request_notes.systemSystem records whether this is a system-generated note (e.g., status changes, label additions). It is needed to measure the GitLab-reported number of system at one GitLab Merge Request Note record per row.

Enables: measure and compare the GitLab-reported number of system in system at one GitLab Merge Request Note record per row.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is a GitLab-reported count at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Type

Developer identifier: merge_request_notes.typeType records the type of the note (e.g., DiffNote, DiscussionNote, or null for regular notes). It is needed to distinguish Merge Request Notes rows by the exact GitLab-returned type value.

Enables: separate Merge Request Notes rows by the exact GitLab-returned type label when comparing type.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Updated At

Developer identifier: merge_request_notes.updated_atUpdated At records when the note was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Request Notes records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request Note object returned for Merge Request Notes; it is interpreted at one GitLab Merge Request Note record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Merge Requests

Developer identifier: merge_requestsMerge Requests covers project merge requests.

Enables: follow each returned code-review request from its repository or project and source revision through reviewer, state, and merge outcome.
Scope: Project merge requests; the connector reads /api/v4/projects/{id}/merge_requests as a changelog stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Allow Collaboration

Developer identifier: merge_requests.allow_collaborationAllow Collaboration records whether collaboration from upstream members is allowed on the source branch. It is needed to distinguish Merge Requests rows by the exact GitLab-returned allow collaboration value.

Enables: select Merge Requests rows where allow_collaboration is true or false when comparing the condition described by Allow Collaboration.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Allow Maintainer To Push

Developer identifier: merge_requests.allow_maintainer_to_pushAllow Maintainer To Push records deprecated alias for allow_collaboration. It is needed to distinguish Merge Requests rows by the exact GitLab-returned allow maintainer to push value.

Enables: select Merge Requests rows where allow_maintainer_to_push is true or false when comparing the condition described by Allow Maintainer To Push.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Approvals Before Merge

Developer identifier: merge_requests.approvals_before_mergeApprovals Before Merge records number of approvals required before merge (project-level setting override). It is needed to measure the GitLab-reported number of approvals required before merge (project-level setting override) at one GitLab Merge Request record per row.

Enables: measure and compare the GitLab-reported number of approvals required before merge (project-level setting override) in approvals_before_merge at one GitLab Merge Request record per row.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.

Assignees

Developer identifier: merge_requests.assigneesAssignees records array of users assigned to review the MR. It is needed to preserve the nested assignees relationship or details on the parent GitLab Merge Request record.

Enables: expand assignees to connect the containing GitLab Merge Request row to its returned assignees entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one returned collection per containing GitLab Merge Request object.

Avatar URL

Developer identifier: merge_requests.assignees.avatar_urlAvatar URL records URL to the user’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is link at one User Reference record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: merge_requests.assignees.idID records unique numeric user ID. It is needed to distinguish repeated deliveries of the same Merge Requests row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Merge Requests and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Locked

Developer identifier: merge_requests.assignees.lockedLocked records whether the user account is locked. It is needed to distinguish Merge Requests rows by the exact GitLab-returned locked value.

Enables: select Merge Requests rows where locked is true or false when comparing the condition described by Locked.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: merge_requests.assignees.nameName records display name of the user. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

Enables: attribute the Merge Requests row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row; the schema uses the Identity.Name scalar.

Public Email

Developer identifier: merge_requests.assignees.public_emailPublic Email records public email address, enriched by the ingestion service via the GitLab Users API. Absent when the user has no public email set or when enrichment is suppressed (e.g. rate-limited backfills). Silver layers must treat this field as optional. It is needed to distinguish Merge Requests rows by the exact GitLab-returned public email value.

Enables: separate Merge Requests rows by the exact GitLab-returned public_email label when comparing public email.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row; the schema uses the Contact.Email scalar; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: merge_requests.assignees.stateState records user account state (e.g., active, blocked). It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

Enables: separate Merge Requests rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: merge_requests.assignees.usernameUser Name records GitLab username. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

Enables: attribute the Merge Requests row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is interpreted at one User Reference record per row.

Web URL

Developer identifier: merge_requests.assignees.web_urlWeb URL records URL to the user’s GitLab profile. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the User Reference object returned for Merge Requests; it is link at one User Reference record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Author

Developer identifier: merge_requests.authorAuthor records user who created the merge request. It is needed to preserve the nested author relationship or details on the parent GitLab Merge Request record.

Enables: expand author to connect the containing GitLab Merge Request row to its returned author entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Blocking Discussions Resolved

Developer identifier: merge_requests.blocking_discussions_resolvedBlocking Discussions Resolved records whether all blocking discussions have been resolved. It is needed to distinguish Merge Requests rows by the exact GitLab-returned blocking discussions resolved value.

Enables: select Merge Requests rows where blocking_discussions_resolved is true or false when comparing the condition described by Blocking Discussions Resolved.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Changes Count

Developer identifier: merge_requests.changes_countChanges Count records number of file changes as a string (may be ‘100+’ for large diffs). It is needed to measure the GitLab-reported number of file changes as a string (may be ‘100+’ for large diffs) at one GitLab Merge Request record per row.

Enables: measure and compare the GitLab-reported number of file changes as a string (may be ‘100+’ for large diffs) in changes_count at one GitLab Merge Request record per row.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.

Closed At

Developer identifier: merge_requests.closed_atClosed At records timestamp when the MR was closed, null if not closed. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by closed_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the schema uses the Temporal.DateTime scalar.

Closed By

Developer identifier: merge_requests.closed_byClosed By records user who closed the MR. It is needed to preserve the nested closed by relationship or details on the parent GitLab Merge Request record.

Enables: expand closed_by to connect the containing GitLab Merge Request row to its returned closed by entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Avatar URL

Developer identifier: merge_requests.closed_by.avatar_urlAvatar URL records URL to the user’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is link at one GitLab User Ref record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: merge_requests.closed_by.idID records unique numeric user ID. It is needed to refer to the same user ref across records without relying on display text.

Enables: match id to user ref references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is an identifier, not a measured quantity.

Locked

Developer identifier: merge_requests.closed_by.lockedLocked records whether the user account is locked. It is needed to distinguish Merge Requests rows by the exact GitLab-returned locked value.

Enables: select Merge Requests rows where locked is true or false when comparing the condition described by Locked.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: merge_requests.closed_by.nameName records display name of the user. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

Enables: attribute the Merge Requests row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row; the schema uses the Identity.Name scalar.

Public Email

Developer identifier: merge_requests.closed_by.public_emailPublic Email records public email address returned by GitLab when present. Silver layers must treat this field as optional. It is needed to distinguish Merge Requests rows by the exact GitLab-returned public email value.

Enables: separate Merge Requests rows by the exact GitLab-returned public_email label when comparing public email.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row; the schema uses the Contact.Email scalar; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: merge_requests.closed_by.stateState records user account state (e.g., active, blocked). It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

Enables: separate Merge Requests rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: merge_requests.closed_by.usernameUser Name records GitLab username. It is needed to attribute this Merge Requests row to the returned person, account, or organization reference.

Enables: attribute the Merge Requests row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is interpreted at one GitLab User Ref record per row.

Web URL

Developer identifier: merge_requests.closed_by.web_urlWeb URL records URL to the user’s GitLab profile. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the GitLab User Ref object returned for Merge Requests; it is link at one GitLab User Ref record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Created At

Developer identifier: merge_requests.created_atCreated At records timestamp when the MR was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the schema uses the Temporal.DateTime scalar.

Description

Developer identifier: merge_requests.descriptionDescription records merge request description body, may contain Markdown. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is description text at one GitLab Merge Request record per row; this is only the content included in the GitLab response for this record.

Detailed Merge Status

Developer identifier: merge_requests.detailed_merge_statusDetailed Merge Status records detailed merge readiness status with specific blocking reasons. It is needed to distinguish Merge Requests rows by the exact GitLab-returned detailed merge status value.

Enables: separate Merge Requests rows by the exact GitLab-returned detailed_merge_status label when comparing detailed merge status.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Diff Refs

Developer identifier: merge_requests.diff_refsDiff Refs records references to the base, head, and start SHAs for the diff. It is needed to preserve the nested diff refs relationship or details on the parent GitLab Merge Request record.

Enables: expand diff_refs to connect the containing GitLab Merge Request row to its returned diff refs entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Base Sha

Developer identifier: merge_requests.diff_refs.base_shaBase Sha records SHA of the merge base commit. It is needed to refer to the same base across records without relying on display text.

Enables: match base_sha to base references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Diff Refs object returned for Merge Requests; it is an identifier, not a measured quantity.

Head Sha

Developer identifier: merge_requests.diff_refs.head_shaHead Sha records SHA of the head commit of the source branch. It is needed to refer to the same head across records without relying on display text.

Enables: match head_sha to head references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Diff Refs object returned for Merge Requests; it is an identifier, not a measured quantity.

Start Sha

Developer identifier: merge_requests.diff_refs.start_shaStart Sha records SHA of the start commit for the diff. It is needed to refer to the same start across records without relying on display text.

Enables: match start_sha to start references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Diff Refs object returned for Merge Requests; it is an identifier, not a measured quantity.

Discussion Locked

Developer identifier: merge_requests.discussion_lockedDiscussion Locked records whether discussions on the MR are locked. It is needed to distinguish Merge Requests rows by the exact GitLab-returned discussion locked value.

Enables: select Merge Requests rows where discussion_locked is true or false when comparing the condition described by Discussion Locked.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Downvotes

Developer identifier: merge_requests.downvotesDownvotes records number of downvote (thumbs down) reactions. It is needed to measure the GitLab-reported number of downvote (thumbs down) reactions at one GitLab Merge Request record per row.

Enables: measure and compare the GitLab-reported number of downvote (thumbs down) reactions in downvotes at one GitLab Merge Request record per row.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.

Draft

Developer identifier: merge_requests.draftDraft records whether the merge request is a draft (work in progress). It is needed to distinguish Merge Requests rows by the exact GitLab-returned draft value.

Enables: select Merge Requests rows where draft is true or false when comparing the condition described by Draft.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Force Remove Source Branch

Developer identifier: merge_requests.force_remove_source_branchForce Remove Source Branch records whether the source branch will be force-removed after merge. It is needed to distinguish Merge Requests rows by the exact GitLab-returned force remove source branch value.

Enables: select Merge Requests rows where force_remove_source_branch is true or false when comparing the condition described by Force Remove Source Branch.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Has Conflicts

Developer identifier: merge_requests.has_conflictsHas Conflicts records whether the MR has merge conflicts. It is needed to distinguish Merge Requests rows by the exact GitLab-returned has conflicts value.

Enables: select Merge Requests rows where has_conflicts is true or false when comparing the condition described by Has Conflicts.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Head Pipeline

Developer identifier: merge_requests.head_pipelineHead Pipeline records pipeline running on the head commit of the source branch. It is needed to preserve the nested head pipeline relationship or details on the parent GitLab Merge Request record.

Enables: expand head_pipeline to connect the containing GitLab Merge Request row to its returned head pipeline entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Created At

Developer identifier: merge_requests.head_pipeline.created_atCreated At records timestamp when the pipeline was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is interpreted at one Pipeline Reference record per row; the schema uses the Temporal.DateTime scalar.

Developer identifier: merge_requests.head_pipeline.idID records unique pipeline ID. It is needed to refer to the same pipeline reference across records without relying on display text.

Enables: match id to pipeline reference references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.

Iid

Developer identifier: merge_requests.head_pipeline.iidIid records project-scoped pipeline ID. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.

Project ID

Developer identifier: merge_requests.head_pipeline.project_idProject ID records ID of the project the pipeline belongs to. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.

Ref

Developer identifier: merge_requests.head_pipeline.refRef records branch or tag name the pipeline ran on. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match ref to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is interpreted at one Pipeline Reference record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Sha

Developer identifier: merge_requests.head_pipeline.shaSha records SHA of the commit the pipeline ran on. It is needed to refer to the same pipeline reference across records without relying on display text.

Enables: match sha to pipeline reference references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is an identifier, not a measured quantity.

Source

Developer identifier: merge_requests.head_pipeline.sourceSource records source that triggered the pipeline (e.g., push, merge_request_event). It is needed to distinguish Merge Requests rows by the exact GitLab-returned source value.

Enables: separate Merge Requests rows by the exact GitLab-returned source label when comparing source.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is interpreted at one Pipeline Reference record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Status

Developer identifier: merge_requests.head_pipeline.statusStatus records pipeline status (e.g., running, pending, success, failed, canceled, skipped). It is needed to distinguish Merge Requests rows by the exact GitLab-returned status value.

Enables: separate Merge Requests rows by the exact GitLab-returned status label when comparing status.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is interpreted at one Pipeline Reference record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Updated At

Developer identifier: merge_requests.head_pipeline.updated_atUpdated At records timestamp when the pipeline was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is interpreted at one Pipeline Reference record per row; the schema uses the Temporal.DateTime scalar.

Web URL

Developer identifier: merge_requests.head_pipeline.web_urlWeb URL records URL to view the pipeline in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the Pipeline Reference object returned for Merge Requests; it is link at one Pipeline Reference record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: merge_requests.idID records unique global numeric identifier for the merge request. It is needed to distinguish repeated deliveries of the same Merge Requests row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Merge Requests and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Iid

Developer identifier: merge_requests.iidIid records project-scoped merge request number. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity.

Imported

Developer identifier: merge_requests.importedImported records whether this merge request was imported from an external source. It is needed to distinguish Merge Requests rows by the exact GitLab-returned imported value.

Enables: select Merge Requests rows where imported is true or false when comparing the condition described by Imported.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Imported From

Developer identifier: merge_requests.imported_fromImported From records the source from which this merge request was imported, if applicable. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare imported_from among Merge Requests records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the value is a GitLab-returned or configured label at the GitLab Merge Request grain rather than a universal taxonomy.

Labels

Developer identifier: merge_requests.labelsLabels records array of label names applied to the MR. It is needed to preserve the nested labels relationship or details on the parent GitLab Merge Request record.

Enables: expand labels to connect the containing GitLab Merge Request row to its returned labels entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one returned collection per containing GitLab Merge Request object.

Merge After

Developer identifier: merge_requests.merge_afterMerge After records timestamp after which the merge request may be merged (auto-merge scheduling). It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by merge_after, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the schema uses the Temporal.DateTime scalar.

Merge Commit Sha

Developer identifier: merge_requests.merge_commit_shaMerge Commit Sha records SHA of the merge commit, null if not yet merged. It is needed to refer to the same merge commit across records without relying on display text.

Enables: match merge_commit_sha to merge commit references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity.

Merge Status

Developer identifier: merge_requests.merge_statusMerge Status records merge readiness status of the MR. It is needed to distinguish Merge Requests rows by the exact GitLab-returned merge status value.

Enables: separate Merge Requests rows by the exact GitLab-returned merge_status label when comparing merge status.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Merge User

Developer identifier: merge_requests.merge_userMerge User records user who triggered the merge (may differ from merged_by for auto-merge). It is needed to preserve the nested merge user relationship or details on the parent GitLab Merge Request record.

Enables: expand merge_user to connect the containing GitLab Merge Request row to its returned merge user entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Merge When Pipeline Succeeds

Developer identifier: merge_requests.merge_when_pipeline_succeedsMerge When Pipeline Succeeds records whether auto-merge is enabled when the pipeline succeeds. It is needed to distinguish Merge Requests rows by the exact GitLab-returned merge when pipeline succeeds value.

Enables: select Merge Requests rows where merge_when_pipeline_succeeds is true or false when comparing the condition described by Merge When Pipeline Succeeds.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Merged At

Developer identifier: merge_requests.merged_atMerged At records timestamp when the MR was merged, null if not yet merged. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by merged_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the schema uses the Temporal.DateTime scalar.

Merged By

Developer identifier: merge_requests.merged_byMerged By records user who merged the MR. It is needed to preserve the nested merged by relationship or details on the parent GitLab Merge Request record.

Enables: expand merged_by to connect the containing GitLab Merge Request row to its returned merged by entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Milestone

Developer identifier: merge_requests.milestoneMilestone records milestone associated with the MR. It is needed to preserve the nested milestone relationship or details on the parent GitLab Merge Request record.

Enables: expand milestone to connect the containing GitLab Merge Request row to its returned milestone entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Created At

Developer identifier: merge_requests.milestone.created_atCreated At records timestamp when the milestone was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is interpreted at one Milestone record per row; the schema uses the Temporal.DateTime scalar.

Description

Developer identifier: merge_requests.milestone.descriptionDescription records milestone description. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is description text at one Milestone record per row; this is only the content included in the GitLab response for this record.

Due Date

Developer identifier: merge_requests.milestone.due_dateDue Date records due date for the milestone. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by due_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is interpreted at one Milestone record per row; the schema uses the Temporal.Date scalar.

Expired

Developer identifier: merge_requests.milestone.expiredExpired records whether the milestone is past its due date. It is needed to distinguish Merge Requests rows by the exact GitLab-returned expired value.

Enables: select Merge Requests rows where expired is true or false when comparing the condition described by Expired.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is interpreted at one Milestone record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Group ID

Developer identifier: merge_requests.milestone.group_idGroup ID records ID of the group the milestone belongs to (for group milestones). It is needed to refer to the same group across records without relying on display text.

Enables: match group_id to group references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is an identifier, not a measured quantity.

Developer identifier: merge_requests.milestone.idID records global milestone ID. It is needed to refer to the same milestone across records without relying on display text.

Enables: match id to milestone references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is an identifier, not a measured quantity.

Iid

Developer identifier: merge_requests.milestone.iidIid records project-scoped milestone ID. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is an identifier, not a measured quantity.

Project ID

Developer identifier: merge_requests.milestone.project_idProject ID records ID of the project the milestone belongs to. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is an identifier, not a measured quantity.

Start Date

Developer identifier: merge_requests.milestone.start_dateStart Date records start date for the milestone. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by start_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is interpreted at one Milestone record per row; the schema uses the Temporal.Date scalar.

State

Developer identifier: merge_requests.milestone.stateState records milestone state (active or closed). It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

Enables: separate Merge Requests rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is interpreted at one Milestone record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Title

Developer identifier: merge_requests.milestone.titleTitle records milestone title. It is needed to inspect the exact title text included with this record.

Enables: inspect the title text returned in title and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is title text at one Milestone record per row; this is only the content included in the GitLab response for this record.

Updated At

Developer identifier: merge_requests.milestone.updated_atUpdated At records timestamp when the milestone was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is interpreted at one Milestone record per row; the schema uses the Temporal.DateTime scalar.

Web URL

Developer identifier: merge_requests.milestone.web_urlWeb URL records URL to view the milestone in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the Milestone object returned for Merge Requests; it is link at one Milestone record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Overflow

Developer identifier: merge_requests.overflowOverflow records whether the diff is too large to display. It is needed to distinguish Merge Requests rows by the exact GitLab-returned overflow value.

Enables: select Merge Requests rows where overflow is true or false when comparing the condition described by Overflow.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Pipeline

Developer identifier: merge_requests.pipelinePipeline records latest pipeline associated with the MR. It is needed to preserve the nested pipeline relationship or details on the parent GitLab Merge Request record.

Enables: expand pipeline to connect the containing GitLab Merge Request row to its returned pipeline entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Prepared At

Developer identifier: merge_requests.prepared_atPrepared At records timestamp when the MR was marked as prepared. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by prepared_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the schema uses the Temporal.DateTime scalar.

Project ID

Developer identifier: merge_requests.project_idProject ID records ID of the project this merge request belongs to. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Rebase In Progress

Developer identifier: merge_requests.rebase_in_progressRebase In Progress records whether a rebase operation is currently in progress. It is needed to distinguish Merge Requests rows by the exact GitLab-returned rebase in progress value.

Enables: select Merge Requests rows where rebase_in_progress is true or false when comparing the condition described by Rebase In Progress.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Reference

Developer identifier: merge_requests.referenceReference records short reference string for the MR (e.g., !123). It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match reference to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

References

Developer identifier: merge_requests.referencesReferences records short and full reference strings for the MR. It is needed to preserve the nested references relationship or details on the parent GitLab Merge Request record.

Enables: expand references to connect the containing GitLab Merge Request row to its returned references entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Full

Developer identifier: merge_requests.references.fullFull records full reference including namespace and project path. It is needed to compare the returned full for individual Merge Requests rows and select rows with a specific full value.

Enables: trace the full relationship returned in full from the References row to its named GitLab context.
Interpretation: GitLab reports this value on the References object returned for Merge Requests; it is interpreted at one References record per row.

Relative

Developer identifier: merge_requests.references.relativeRelative records relative reference including project path. It is needed to compare the returned relative for individual Merge Requests rows and select rows with a specific relative value.

Enables: trace the relative relationship returned in relative from the References row to its named GitLab context.
Interpretation: GitLab reports this value on the References object returned for Merge Requests; it is interpreted at one References record per row.

Short

Developer identifier: merge_requests.references.shortShort records short reference (e.g., !123). It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match short to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the References object returned for Merge Requests; it is interpreted at one References record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Reviewers

Developer identifier: merge_requests.reviewersReviewers records array of users designated as reviewers. It is needed to preserve the nested reviewers relationship or details on the parent GitLab Merge Request record.

Enables: expand reviewers to connect the containing GitLab Merge Request row to its returned reviewers entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one returned collection per containing GitLab Merge Request object.

Sha

Developer identifier: merge_requests.shaSha records SHA of the latest commit on the source branch at the head of the MR. It is needed to refer to the same merge request across records without relying on display text.

Enables: match sha to merge request references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity.

Should Remove Source Branch

Developer identifier: merge_requests.should_remove_source_branchShould Remove Source Branch records whether the source branch should be deleted after merge. It is needed to distinguish Merge Requests rows by the exact GitLab-returned should remove source branch value.

Enables: select Merge Requests rows where should_remove_source_branch is true or false when comparing the condition described by Should Remove Source Branch.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Source Branch

Developer identifier: merge_requests.source_branchSource Branch records name of the source branch. It is needed to distinguish Merge Requests rows by the exact GitLab-returned source branch value.

Enables: separate Merge Requests rows by the exact GitLab-returned source_branch label when comparing source branch.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Source Project ID

Developer identifier: merge_requests.source_project_idSource Project ID records ID of the source project (may differ from project_id for cross-project MRs). It is needed to refer to the same source project across records without relying on display text.

Enables: match source_project_id to source project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity; classification values are GitLab-returned labels rather than a universal taxonomy.

Squash

Developer identifier: merge_requests.squashSquash records whether commits will be squashed on merge. It is needed to distinguish Merge Requests rows by the exact GitLab-returned squash value.

Enables: select Merge Requests rows where squash is true or false when comparing the condition described by Squash.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Squash Commit Sha

Developer identifier: merge_requests.squash_commit_shaSquash Commit Sha records SHA of the squash commit, null if squash was not used. It is needed to refer to the same squash commit across records without relying on display text.

Enables: match squash_commit_sha to squash commit references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity.

Squash On Merge

Developer identifier: merge_requests.squash_on_mergeSquash On Merge records whether squash on merge is enabled. It is needed to distinguish Merge Requests rows by the exact GitLab-returned squash on merge value.

Enables: select Merge Requests rows where squash_on_merge is true or false when comparing the condition described by Squash On Merge.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

State

Developer identifier: merge_requests.stateState records current state of the merge request. It is needed to distinguish Merge Requests rows by the exact GitLab-returned state value.

Enables: separate Merge Requests rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Target Branch

Developer identifier: merge_requests.target_branchTarget Branch records name of the target branch. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match target_branch to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Target Project ID

Developer identifier: merge_requests.target_project_idTarget Project ID records ID of the target project. It is needed to refer to the same target project across records without relying on display text.

Enables: match target_project_id to target project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is an identifier, not a measured quantity.

Task Completion Status

Developer identifier: merge_requests.task_completion_statusTask Completion Status records completion status of tasks/checklists in the MR description. It is needed to preserve the nested task completion status relationship or details on the parent GitLab Merge Request record.

Enables: expand task_completion_status to connect the containing GitLab Merge Request row to its returned task completion status entries.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Completed Count

Developer identifier: merge_requests.task_completion_status.completed_countCompleted Count records number of completed tasks. It is needed to measure the GitLab-reported number of completed tasks at one Task Completion Status record per row.

Enables: measure and compare the GitLab-reported number of completed tasks in completed_count at one Task Completion Status record per row.
Interpretation: GitLab reports this value on the Task Completion Status object returned for Merge Requests; it is a GitLab-reported count at one Task Completion Status record per row.

Count

Developer identifier: merge_requests.task_completion_status.countCount records total number of tasks. It is needed to measure the GitLab-reported number of tasks at one Task Completion Status record per row.

Enables: measure and compare the GitLab-reported number of tasks in count at one Task Completion Status record per row.
Interpretation: GitLab reports this value on the Task Completion Status object returned for Merge Requests; it is a GitLab-reported count at one Task Completion Status record per row.

Time Stats

Developer identifier: merge_requests.time_statsTime Stats records time tracking statistics for the MR. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by time_stats, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is one nested object per containing GitLab Merge Request object when present.

Human Time Estimate

Developer identifier: merge_requests.time_stats.human_time_estimateHuman Time Estimate records human-readable estimated time (e.g., ‘3h 30m’). It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by human_time_estimate, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Time Stats object returned for Merge Requests; it is interpreted at one Time Stats record per row.

Human Total Time Spent

Developer identifier: merge_requests.time_stats.human_total_time_spentHuman Total Time Spent records human-readable total time spent. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by human_total_time_spent, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Time Stats object returned for Merge Requests; it is interpreted at one Time Stats record per row.

Time Estimate

Developer identifier: merge_requests.time_stats.time_estimateTime Estimate records estimated time in seconds. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by time_estimate, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Time Stats object returned for Merge Requests; its unit or granularity is seconds.

Total Time Spent

Developer identifier: merge_requests.time_stats.total_time_spentTotal Time Spent records total time spent in seconds. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by total_time_spent, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Time Stats object returned for Merge Requests; its unit or granularity is seconds.

Title

Developer identifier: merge_requests.titleTitle records merge request title. It is needed to inspect the exact title text included with this record.

Enables: inspect the title text returned in title and attribute it to the same record’s repository or project, work-item number, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is title text at one GitLab Merge Request record per row; this is only the content included in the GitLab response for this record.

Updated At

Developer identifier: merge_requests.updated_atUpdated At records timestamp when the MR was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Merge Requests records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Upvotes

Developer identifier: merge_requests.upvotesUpvotes records number of upvote (thumbs up) reactions. It is needed to measure the GitLab-reported number of upvote (thumbs up) reactions at one GitLab Merge Request record per row.

Enables: measure and compare the GitLab-reported number of upvote (thumbs up) reactions in upvotes at one GitLab Merge Request record per row.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.

User Notes Count

Developer identifier: merge_requests.user_notes_countUser Notes Count records number of user-created notes (comments) on the MR. It is needed to measure the GitLab-reported number of user-created notes (comments) on the MR at one GitLab Merge Request record per row.

Enables: measure and compare the GitLab-reported number of user-created notes (comments) on the MR in user_notes_count at one GitLab Merge Request record per row.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is a GitLab-reported count at one GitLab Merge Request record per row.

Web URL

Developer identifier: merge_requests.web_urlWeb URL records URL to view the merge request in the GitLab web UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Merge Requests record as provenance.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is link at one GitLab Merge Request record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Work In Progress

Developer identifier: merge_requests.work_in_progressWork In Progress records deprecated alias for draft. It is needed to distinguish Merge Requests rows by the exact GitLab-returned work in progress value.

Enables: select Merge Requests rows where work_in_progress is true or false when comparing the condition described by Work In Progress.
Interpretation: GitLab reports this value on the GitLab Merge Request object returned for Merge Requests; it is interpreted at one GitLab Merge Request record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Pipelines

Developer identifier: pipelinesPipelines covers project CI/CD pipelines.

Enables: trace each returned CI/CD pipeline to its project, revision, trigger source, status, user, and timing values.
Scope: Project CI/CD pipelines; the connector reads /api/v4/projects/{id}/pipelines as a changelog stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Before Sha

Developer identifier: pipelines.before_shaBefore Sha records SHA of the commit just before the pipeline source commit. It is needed to refer to the same before across records without relying on display text.

Enables: match before_sha to before references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is an identifier, not a measured quantity.

Committed At

Developer identifier: pipelines.committed_atCommitted At records timestamp of the commit that triggered the pipeline. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Pipelines records by committed_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Coverage

Developer identifier: pipelines.coverageCoverage records code coverage percentage reported by the pipeline. It is needed to measure the code-coverage percentage reported for this pipeline execution.

Enables: compare coverage at one pipeline grain while preserving the project, revision, and pipeline identifiers.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; its unit or granularity is percent; the value is a GitLab-reported percentage string and does not by itself establish test quality or change causality.

Created At

Developer identifier: pipelines.created_atCreated At records timestamp when the pipeline was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Pipelines records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Duration

Developer identifier: pipelines.durationDuration records total duration of the pipeline in seconds (wall time from start to finish). It is needed to measure the exact duration reported for one GitLab Pipeline record using the GitLab duration encoding described by the field.

Enables: measure and compare duration per GitLab Pipeline record in seconds.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; its unit or granularity is seconds.

Finished At

Developer identifier: pipelines.finished_atFinished At records timestamp when the pipeline finished. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Pipelines records by finished_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Developer identifier: pipelines.idID records unique numeric identifier for the pipeline. It is needed to distinguish repeated deliveries of the same Pipelines row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Pipelines and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Iid

Developer identifier: pipelines.iidIid records project-scoped pipeline number, human-readable reference. It is needed to refer to the same iid across records without relying on display text.

Enables: match iid to iid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is an identifier, not a measured quantity.

Name

Developer identifier: pipelines.nameName records name of the pipeline, if set via workflow:name in CI config. It is needed to compare the exact name configuration returned for this GitLab Pipeline record.

Enables: compare the exact name configuration returned for each GitLab Pipeline record and select records with the configuration under review.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row.

Project ID

Developer identifier: pipelines.project_idProject ID records ID of the project this pipeline belongs to. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is an identifier, not a measured quantity.

Queued Duration

Developer identifier: pipelines.queued_durationQueued Duration records total time in seconds the pipeline spent queued before running. It is needed to measure the exact duration reported for one GitLab Pipeline record using the GitLab duration encoding described by the field.

Enables: measure and compare queued_duration per GitLab Pipeline record in seconds.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; its unit or granularity is seconds.

Ref

Developer identifier: pipelines.refRef records branch or tag name that triggered the pipeline. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match ref to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Sha

Developer identifier: pipelines.shaSha records full commit SHA that triggered the pipeline. It is needed to refer to the same pipeline across records without relying on display text.

Enables: match sha to pipeline references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is an identifier, not a measured quantity.

Source

Developer identifier: pipelines.sourceSource records what triggered the pipeline. It is needed to distinguish Pipelines rows by the exact GitLab-returned source value.

Enables: separate Pipelines rows by the exact GitLab-returned source label when comparing source.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Started At

Developer identifier: pipelines.started_atStarted At records timestamp when the pipeline started running. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Pipelines records by started_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Status

Developer identifier: pipelines.statusStatus records current status of the pipeline. It is needed to distinguish Pipelines rows by the exact GitLab-returned status value.

Enables: separate Pipelines rows by the exact GitLab-returned status label when comparing status.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Tag

Developer identifier: pipelines.tagTag records whether the pipeline was triggered by a tag. It is needed to distinguish Pipelines rows by the exact GitLab-returned tag value.

Enables: select Pipelines rows where tag is true or false when comparing the condition described by Tag.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Updated At

Developer identifier: pipelines.updated_atUpdated At records timestamp when the pipeline was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Pipelines records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

User

Developer identifier: pipelines.userUser records the user who triggered the pipeline. It is needed to preserve the nested user relationship or details on the parent GitLab Pipeline record.

Enables: expand user to connect the containing GitLab Pipeline row to its returned user entries.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is one nested object per containing GitLab Pipeline object when present.

Avatar URL

Developer identifier: pipelines.user.avatar_urlAvatar URL records URL to the user’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Pipelines record as provenance.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is link at one Pipeline User record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: pipelines.user.idID records unique numeric identifier of the user. It is needed to refer to the same pipeline user across records without relying on display text.

Enables: match id to pipeline user references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is an identifier, not a measured quantity.

Locked

Developer identifier: pipelines.user.lockedLocked records whether the user account is locked. It is needed to distinguish Pipelines rows by the exact GitLab-returned locked value.

Enables: select Pipelines rows where locked is true or false when comparing the condition described by Locked.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is interpreted at one Pipeline User record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: pipelines.user.nameName records display name of the user. It is needed to attribute this Pipelines row to the returned person, account, or organization reference.

Enables: attribute the Pipelines row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is interpreted at one Pipeline User record per row; the schema uses the Identity.Name scalar.

State

Developer identifier: pipelines.user.stateState records account state of the user (e.g., active, blocked). It is needed to distinguish Pipelines rows by the exact GitLab-returned state value.

Enables: separate Pipelines rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is interpreted at one Pipeline User record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: pipelines.user.usernameUser Name records GitLab username. It is needed to attribute this Pipelines row to the returned person, account, or organization reference.

Enables: attribute the Pipelines row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is interpreted at one Pipeline User record per row.

Web URL

Developer identifier: pipelines.user.web_urlWeb URL records URL to the user’s GitLab profile page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Pipelines record as provenance.
Interpretation: GitLab reports this value on the Pipeline User object returned for Pipelines; it is link at one Pipeline User record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Web URL

Developer identifier: pipelines.web_urlWeb URL records URL to view the pipeline in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Pipelines record as provenance.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is link at one GitLab Pipeline record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Yaml Errors

Developer identifier: pipelines.yaml_errorsYaml Errors records errors found in the CI YAML configuration, if any. It is needed to compare the exact yaml errors configuration returned for this GitLab Pipeline record.

Enables: compare the exact yaml_errors configuration returned for each GitLab Pipeline record and select records with the configuration under review.
Interpretation: GitLab reports this value on the GitLab Pipeline object returned for Pipelines; it is interpreted at one GitLab Pipeline record per row.

Project Commits

Developer identifier: project_commitsProject Commits covers project repository commits.

Enables: trace each returned revision to its repository or project, author and committer identities, message, and provider-reported commit times.
Scope: Project repository commits; the connector reads /api/v4/projects/{id}/repository/commits as an event stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Author Email

Developer identifier: project_commits.author_emailAuthor Email records email of the commit author. Used for cross-system identity resolution. It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

Enables: attribute the Project Commits row to the returned person or account and match the exact author_email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Contact.Email scalar.

Author Name

Developer identifier: project_commits.author_nameAuthor Name records name of the commit author as recorded in Git. It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

Enables: attribute the Project Commits row to the returned person or account and match the exact author_name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row.

Authored Date

Developer identifier: project_commits.authored_dateAuthored Date records timestamp when the commit was originally authored. Tracks when code was actually written. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Commits records by authored_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Temporal.DateTime scalar.

Committed Date

Developer identifier: project_commits.committed_dateCommitted Date records timestamp when the commit was committed. Used as incremental sync cursor and activity timeline signal. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Commits records by committed_date, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row; the connector also declares it for record ordering; the schema assigns the event_time semantic role; the schema uses the Temporal.DateTime scalar.

Committer Email

Developer identifier: project_commits.committer_emailCommitter Email records email of the committer. It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

Enables: attribute the Project Commits row to the returned person or account and match the exact committer_email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Contact.Email scalar.

Committer Name

Developer identifier: project_commits.committer_nameCommitter Name records name of the person who committed the code (may differ from author in rebases/cherry-picks). It is needed to attribute this Project Commits row to the returned person, account, or organization reference.

Enables: attribute the Project Commits row to the returned person or account and match the exact committer_name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row.

Created At

Developer identifier: project_commits.created_atCreated At records timestamp when the commit record was created in GitLab. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Commits records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row; the schema uses the Temporal.DateTime scalar.

Extended Trailers

Developer identifier: project_commits.extended_trailersExtended Trailers records extended Git trailers from the commit message, supporting multiple values per key. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in extended_trailers and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; the schema uses the Generic.JSON scalar; this is only the content included in the GitLab response for this record.

Developer identifier: project_commits.idID records full SHA hash of the commit. Primary key for commit-level attribution and cross-referencing. It is needed to distinguish repeated deliveries of the same Project Commits row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Project Commits and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Last Pipeline

Developer identifier: project_commits.last_pipelineLast Pipeline records summary of the last CI/CD pipeline that ran for this commit. It is needed to preserve the nested last pipeline relationship or details on the parent GitLab Project Commit record.

Enables: expand last_pipeline to connect the containing GitLab Project Commit row to its returned last pipeline entries.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is one nested object per containing GitLab Project Commit object when present.

Created At

Developer identifier: project_commits.last_pipeline.created_atCreated At records timestamp when the pipeline was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Commits records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is interpreted at one Commit Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Developer identifier: project_commits.last_pipeline.idID records numeric ID of the pipeline. It is needed to refer to the same commit pipeline across records without relying on display text.

Enables: match id to commit pipeline references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is an identifier, not a measured quantity.

Ref

Developer identifier: project_commits.last_pipeline.refRef records branch or tag name that triggered the pipeline. It is needed to link the row to the exact GitLab branch, tag, revision, or work-item reference named by this field.

Enables: match ref to the returned branch, tag, commit SHA, or work-item reference on related GitLab records.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is interpreted at one Commit Pipeline record per row; the value is a provider reference at the containing record grain and may be a name, shorthand, or immutable revision depending on the field description.

Sha

Developer identifier: project_commits.last_pipeline.shaSha records SHA of the commit the pipeline ran against. It is needed to refer to the same commit pipeline across records without relying on display text.

Enables: match sha to commit pipeline references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is an identifier, not a measured quantity.

Status

Developer identifier: project_commits.last_pipeline.statusStatus records current status of the pipeline. It is needed to distinguish Project Commits rows by the exact GitLab-returned status value.

Enables: separate Project Commits rows by the exact GitLab-returned status label when comparing status.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is interpreted at one Commit Pipeline record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Updated At

Developer identifier: project_commits.last_pipeline.updated_atUpdated At records timestamp when the pipeline was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Commits records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is interpreted at one Commit Pipeline record per row; the schema uses the Temporal.DateTime scalar.

Web URL

Developer identifier: project_commits.last_pipeline.web_urlWeb URL records URL to view the pipeline in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Project Commits record as provenance.
Interpretation: GitLab reports this value on the Commit Pipeline object returned for Project Commits; it is link at one Commit Pipeline record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Message

Developer identifier: project_commits.messageMessage records full commit message including title and body. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in message and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.

Parent IDs

Developer identifier: project_commits.parent_idsParent IDs records array of parent commit SHA hashes. Merge commits will have multiple parents. It is needed to preserve the nested parent i ds relationship or details on the parent GitLab Project Commit record.

Enables: expand parent_ids to connect the containing GitLab Project Commit row to its returned parent i ds entries.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is one returned collection per containing GitLab Project Commit object.

Project ID

Developer identifier: project_commits.project_idProject ID records parent project id injected by the ingestor when iterating per-project (from the (id) path parameter in the project_commits endpoint). Not part of the upstream GitLab API response; written into each row at bronze ingestion time. It is needed to refer to the same project across records without relying on display text.

Enables: match project_id to project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab’s child response does not supply this field; the connector injects parent context into each child row; it is an identifier, not a measured quantity.

Short ID

Developer identifier: project_commits.short_idShort ID records short SHA hash of the commit, typically 8 characters. Human-readable commit reference. It is needed to refer to the same short across records without relying on display text.

Enables: match short_id to short references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is an identifier, not a measured quantity.

Stats

Developer identifier: project_commits.statsStats records diff statistics for the commit including lines added, deleted, and total changes. Only present when with_stats=true. It is needed to preserve the nested stats relationship or details on the parent GitLab Project Commit record.

Enables: expand stats to connect the containing GitLab Project Commit row to its returned stats entries.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is one nested object per containing GitLab Project Commit object when present.

Additions

Developer identifier: project_commits.stats.additionsAdditions records number of lines added in this commit. Quantifies code contribution volume. It is needed to measure the GitLab-reported number of lines added in this commit. Quantifies code contribution volume at one Commit Stats record per row.

Enables: measure and compare the GitLab-reported number of lines added in this commit. Quantifies code contribution volume in additions at one Commit Stats record per row.
Interpretation: GitLab reports this value on the Commit Stats object returned for Project Commits; it is a GitLab-reported count at one Commit Stats record per row.

Deletions

Developer identifier: project_commits.stats.deletionsDeletions records number of lines deleted in this commit. It is needed to measure the GitLab-reported number of lines deleted in this commit at one Commit Stats record per row.

Enables: measure and compare the GitLab-reported number of lines deleted in this commit in deletions at one Commit Stats record per row.
Interpretation: GitLab reports this value on the Commit Stats object returned for Project Commits; it is a GitLab-reported count at one Commit Stats record per row.

Total

Developer identifier: project_commits.stats.totalTotal records total number of lines changed (additions + deletions). It is needed to measure the GitLab-reported number of lines changed (additions + deletions) at one Commit Stats record per row.

Enables: measure and compare the GitLab-reported number of lines changed (additions + deletions) in total at one Commit Stats record per row.
Interpretation: GitLab reports this value on the Commit Stats object returned for Project Commits; it is a GitLab-reported count at one Commit Stats record per row.

Status

Developer identifier: project_commits.statusStatus records status of the latest pipeline associated with this commit, if any. It is needed to distinguish Project Commits rows by the exact GitLab-returned status value.

Enables: separate Project Commits rows by the exact GitLab-returned status label when comparing status.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is interpreted at one GitLab Project Commit record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Title

Developer identifier: project_commits.titleTitle records first line of the commit message. Enables commit message analysis for work categorization. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in title and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; this is only the content included in the GitLab response for this record.

Trailers

Developer identifier: project_commits.trailersTrailers records git trailers parsed from the commit message as key-value pairs (e.g., Signed-off-by, Co-authored-by). It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in trailers and attribute it to the same record’s repository or project, revision, author, and timestamp where returned.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is commit message at one GitLab Project Commit record per row; the schema uses the Generic.JSON scalar; this is only the content included in the GitLab response for this record.

Web URL

Developer identifier: project_commits.web_urlWeb URL records URL to view the commit in the GitLab web interface. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Project Commits record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Commit object returned for Project Commits; it is link at one GitLab Project Commit record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Project Members

Developer identifier: project_membersProject Members covers members of a project (including inherited members).

Enables: map the GitLab accounts and memberships represented by Project Members records and trace a returned access assignment to its account or group.
Scope: Members of a project (including inherited members); the connector reads /api/v4/projects/{id}/members/all as a snapshot stream in full mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

Access Level

Developer identifier: project_members.access_levelAccess Level records permission level granted to the member (10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact access_level access value with the resource, account, or membership represented by the same Project Members row.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Avatar URL

Developer identifier: project_members.avatar_urlAvatar URL records URL to the member’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Project Members record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is link at one GitLab Project Member record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Created At

Developer identifier: project_members.created_atCreated At records timestamp when the membership was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Members records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Created By

Developer identifier: project_members.created_byCreated By records user who added this member to the project. It is needed to preserve the nested created by relationship or details on the parent GitLab Project Member record.

Enables: expand created_by to connect the containing GitLab Project Member row to its returned created by entries.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is one nested object per containing GitLab Project Member object when present.

Avatar URL

Developer identifier: project_members.created_by.avatar_urlAvatar URL records URL to the creator’s avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Project Members record as provenance.
Interpretation: GitLab reports this value on the Member Created By object returned for Project Members; it is link at one Member Created By record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: project_members.created_by.idID records user ID of the creator. It is needed to refer to the same member created by across records without relying on display text.

Enables: match id to member created by references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Member Created By object returned for Project Members; it is an identifier, not a measured quantity.

Name

Developer identifier: project_members.created_by.nameName records display name of the creator. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

Enables: attribute the Project Members row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Member Created By object returned for Project Members; it is interpreted at one Member Created By record per row; the schema uses the Identity.Name scalar.

State

Developer identifier: project_members.created_by.stateState records account state of the creator. It is needed to distinguish Project Members rows by the exact GitLab-returned state value.

Enables: separate Project Members rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the Member Created By object returned for Project Members; it is interpreted at one Member Created By record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: project_members.created_by.usernameUser Name records GitLab username of the creator. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

Enables: attribute the Project Members row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the Member Created By object returned for Project Members; it is interpreted at one Member Created By record per row.

Web URL

Developer identifier: project_members.created_by.web_urlWeb URL records URL to the creator’s GitLab profile page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Project Members record as provenance.
Interpretation: GitLab reports this value on the Member Created By object returned for Project Members; it is link at one Member Created By record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: project_members.emailEmail records email address of the member, if visible. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

Enables: attribute the Project Members row to the returned person or account and match the exact email value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; the schema uses the Contact.Email scalar.

Expires At

Developer identifier: project_members.expires_atExpires At records membership expiration date if set (YYYY-MM-DD format). It is needed to place the record at the time or date reported for this event or state.

Enables: bound Project Members records by expires_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; the schema uses the Temporal.Date scalar.

Group SAML Identity

Developer identifier: project_members.group_saml_identityGroup SAML Identity records SAML identity information if the member authenticated via group SAML. It is needed to preserve the nested group saml identity relationship or details on the parent GitLab Project Member record.

Enables: expand group_saml_identity to connect the containing GitLab Project Member row to its returned group saml identity entries.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is one nested object per containing GitLab Project Member object when present.

Extern Uid

Developer identifier: project_members.group_saml_identity.extern_uidExtern Uid records external UID from the SAML identity provider. It is needed to refer to the same extern uid across records without relying on display text.

Enables: match extern_uid to extern uid references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Group Saml Identity object returned for Project Members; it is an identifier, not a measured quantity.

Provider

Developer identifier: project_members.group_saml_identity.providerProvider records name of the SAML identity provider. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare provider among Project Members records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the Group Saml Identity object returned for Project Members; it is interpreted at one Group Saml Identity record per row; the value is a GitLab-returned or configured label at the Group Saml Identity grain rather than a universal taxonomy.

SAML Provider ID

Developer identifier: project_members.group_saml_identity.saml_provider_idSAML Provider ID records ID of the SAML provider configuration. It is needed to refer to the same saml provider across records without relying on display text.

Enables: match saml_provider_id to saml provider references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the Group Saml Identity object returned for Project Members; it is an identifier, not a measured quantity.

Developer identifier: project_members.idID records user ID of the member. It is needed to distinguish repeated deliveries of the same Project Members row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Project Members and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Is Using Seat

Developer identifier: project_members.is_using_seatIs Using Seat records whether the member is using a license seat. It is needed to distinguish Project Members rows by the exact GitLab-returned is using seat value.

Enables: select Project Members rows where is_using_seat is true or false when comparing the condition described by Is Using Seat.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Membership State

Developer identifier: project_members.membership_stateMembership State records state of the membership (active, awaiting, etc.). It is needed to distinguish Project Members rows by the exact GitLab-returned membership state value.

Enables: separate Project Members rows by the exact GitLab-returned membership_state label when comparing membership state.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: project_members.nameName records display name of the member. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

Enables: attribute the Project Members row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; the schema uses the Identity.Name scalar.

State

Developer identifier: project_members.stateState records account state of the user (active, blocked, etc.). It is needed to distinguish Project Members rows by the exact GitLab-returned state value.

Enables: separate Project Members rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: project_members.usernameUser Name records GitLab username of the member. It is needed to attribute this Project Members row to the returned person, account, or organization reference.

Enables: attribute the Project Members row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is interpreted at one GitLab Project Member record per row.

Web URL

Developer identifier: project_members.web_urlWeb URL records URL to the member’s GitLab profile page. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Project Members record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Member object returned for Project Members; it is link at one GitLab Project Member record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Projects

Developer identifier: projectsProjects covers GitLab projects the authenticated user is a member of.

Enables: inventory returned projects and correlate each project with its namespace, owner, visibility, default branch, and last reported update.
Scope: GitLab projects the authenticated user is a member of; the connector reads /api/v4/projects as a snapshot stream in incremental mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. This stream has no deletion signal, so a missing row does not establish that the GitLab record was deleted.

Provider-defined fields may also be returned for this data stream.

Links

Developer identifier: projects._linksLinks records hypermedia links for the project. GitLab returns this object under the _links key; the whole object was dropped when declared as links. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by _links while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is link at one GitLab Project record per row; the returned link or template does not establish that the current credential can retrieve its target.

Cluster Agents

Developer identifier: projects._links.cluster_agentsCluster Agents records API URL for cluster agents. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by cluster_agents while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Events

Developer identifier: projects._links.eventsEvents records API URL for project events. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by events while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Issues

Developer identifier: projects._links.issuesIssues records API URL for project issues. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by issues while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target; classification values are GitLab-returned labels rather than a universal taxonomy.

Labels

Developer identifier: projects._links.labelsLabels records API URL for project labels. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by labels while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Members

Developer identifier: projects._links.membersMembers records API URL for project members. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by members while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Merge Requests

Developer identifier: projects._links.merge_requestsMerge Requests records API URL for project merge requests. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by merge_requests while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Repo Branches

Developer identifier: projects._links.repo_branchesRepo Branches records API URL for repository branches. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by repo_branches while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Self

Developer identifier: projects._links.selfSelf records API URL for this project. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by self while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project Links object returned for Projects; it is link at one GitLab Project Links record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Allow Merge On Skipped Pipeline

Developer identifier: projects.allow_merge_on_skipped_pipelineAllow Merge On Skipped Pipeline records whether merges are allowed when the pipeline is skipped. It is needed to distinguish Projects rows by the exact GitLab-returned allow merge on skipped pipeline value.

Enables: select Projects rows where allow_merge_on_skipped_pipeline is true or false when comparing the condition described by Allow Merge On Skipped Pipeline.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Analytics Access Level

Developer identifier: projects.analytics_access_levelAnalytics Access Level records access level for analytics. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact analytics_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Archived

Developer identifier: projects.archivedArchived records whether the project is archived. It is needed to distinguish Projects rows by the exact GitLab-returned archived value.

Enables: select Projects rows where archived is true or false when comparing the condition described by Archived.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Auto Cancel Pending Pipelines

Developer identifier: projects.auto_cancel_pending_pipelinesAuto Cancel Pending Pipelines records whether pending pipelines are auto-cancelled. It is needed to distinguish Projects rows by the exact GitLab-returned auto cancel pending pipelines value.

Enables: select Projects rows where auto_cancel_pending_pipelines is true or false when comparing the condition described by Auto Cancel Pending Pipelines.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Auto Devops Deploy Strategy

Developer identifier: projects.auto_devops_deploy_strategyAuto Devops Deploy Strategy records auto DevOps deployment strategy. It is needed to distinguish Projects rows by the exact GitLab-returned auto devops deploy strategy value.

Enables: separate Projects rows by the exact GitLab-returned auto_devops_deploy_strategy label when comparing auto devops deploy strategy.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Auto Devops Enabled

Developer identifier: projects.auto_devops_enabledAuto Devops Enabled records whether Auto DevOps is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned auto devops enabled value.

Enables: select Projects rows where auto_devops_enabled is true or false when comparing the condition described by Auto Devops Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Autoclose Referenced Issues

Developer identifier: projects.autoclose_referenced_issuesAutoclose Referenced Issues records whether referenced issues are automatically closed on merge. It is needed to distinguish Projects rows by the exact GitLab-returned autoclose referenced issues value.

Enables: select Projects rows where autoclose_referenced_issues is true or false when comparing the condition described by Autoclose Referenced Issues.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Avatar URL

Developer identifier: projects.avatar_urlAvatar URL records URL to the project avatar image. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is link at one GitLab Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Build Coverage Regex

Developer identifier: projects.build_coverage_regexBuild Coverage Regex records regex for extracting code coverage from build output. It is needed to measure the code-coverage percentage reported for this pipeline execution.

Enables: compare build_coverage_regex at one pipeline grain while preserving the project, revision, and pipeline identifiers.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the value is a GitLab-reported percentage string and does not by itself establish test quality or change causality.

Build Git Strategy

Developer identifier: projects.build_git_strategyBuild Git Strategy records git strategy for CI/CD builds (fetch or clone). It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare build_git_strategy among Projects records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the value is a GitLab-returned or configured label at the GitLab Project grain rather than a universal taxonomy.

Build Timeout

Developer identifier: projects.build_timeoutBuild Timeout records CI/CD build timeout in seconds. It is needed to measure the reported build timeout for one gitlab project record.

Enables: measure and compare build_timeout per GitLab Project record in seconds.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; its unit or granularity is seconds.

Builds Access Level

Developer identifier: projects.builds_access_levelBuilds Access Level records access level for CI/CD builds. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact builds_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Can Create Merge Request In

Developer identifier: projects.can_create_merge_request_inCan Create Merge Request In records whether the current user can create merge requests in this project. It is needed to distinguish Projects rows by the exact GitLab-returned can create merge request in value.

Enables: select Projects rows where can_create_merge_request_in is true or false when comparing the condition described by Can Create Merge Request In.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Allow Fork Pipelines To Run In Parent Project

Developer identifier: projects.ci_allow_fork_pipelines_to_run_in_parent_projectCi Allow Fork Pipelines To Run In Parent Project records whether fork pipelines can run in the parent project. It is needed to distinguish Projects rows by the exact GitLab-returned ci allow fork pipelines to run in parent project value.

Enables: select Projects rows where ci_allow_fork_pipelines_to_run_in_parent_project is true or false when comparing the condition described by Ci Allow Fork Pipelines To Run In Parent Project.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Config Path

Developer identifier: projects.ci_config_pathCi Config Path records path to the CI/CD configuration file. It is needed to compare the exact ci config path configuration returned for this GitLab Project record.

Enables: compare the exact ci_config_path configuration returned for each GitLab Project record and select records with the configuration under review.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row.

Ci Default Git Depth

Developer identifier: projects.ci_default_git_depthCi Default Git Depth records default git depth for CI/CD pipelines. It is needed to distinguish Projects rows by the exact GitLab-returned ci default git depth value.

Enables: separate Projects rows by the exact GitLab-returned ci_default_git_depth label when comparing ci default git depth.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Forward Deployment Enabled

Developer identifier: projects.ci_forward_deployment_enabledCi Forward Deployment Enabled records whether forward deployment is enabled for CI/CD. It is needed to distinguish Projects rows by the exact GitLab-returned ci forward deployment enabled value.

Enables: select Projects rows where ci_forward_deployment_enabled is true or false when comparing the condition described by Ci Forward Deployment Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Forward Deployment Rollback Allowed

Developer identifier: projects.ci_forward_deployment_rollback_allowedCi Forward Deployment Rollback Allowed records whether rollback is allowed for forward deployments. It is needed to distinguish Projects rows by the exact GitLab-returned ci forward deployment rollback allowed value.

Enables: select Projects rows where ci_forward_deployment_rollback_allowed is true or false when comparing the condition described by Ci Forward Deployment Rollback Allowed.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Job Token Scope Enabled

Developer identifier: projects.ci_job_token_scope_enabledCi Job Token Scope Enabled records whether CI job token scope is enabled. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact ci_job_token_scope_enabled access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Restrict Pipeline Cancellation Role

Developer identifier: projects.ci_restrict_pipeline_cancellation_roleCi Restrict Pipeline Cancellation Role records role required to cancel pipelines. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact ci_restrict_pipeline_cancellation_role access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Ci Separated Caches

Developer identifier: projects.ci_separated_cachesCi Separated Caches records whether CI/CD caches are separated by ref. It is needed to distinguish Projects rows by the exact GitLab-returned ci separated caches value.

Enables: select Projects rows where ci_separated_caches is true or false when comparing the condition described by Ci Separated Caches.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Compliance Frameworks

Developer identifier: projects.compliance_frameworksCompliance Frameworks records compliance frameworks applied to the project. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: expand compliance_frameworks to examine the returned compliance frameworks details for the containing GitLab Project record.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; a returned framework label or feature setting does not demonstrate that a framework requirement is satisfied.

Container Registry Access Level

Developer identifier: projects.container_registry_access_levelContainer Registry Access Level records access level for the container registry. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact container_registry_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Container Registry Enabled

Developer identifier: projects.container_registry_enabledContainer Registry Enabled records whether the container registry is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned container registry enabled value.

Enables: select Projects rows where container_registry_enabled is true or false when comparing the condition described by Container Registry Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Container Registry Image Prefix

Developer identifier: projects.container_registry_image_prefixContainer Registry Image Prefix records prefix for container registry images. It is needed to inventory the exact GitLab-reported configuration or classification represented by this field.

Enables: compare container_registry_image_prefix among Projects records when reconciling this specific configuration, source, or classification.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the value is a GitLab-returned or configured label at the GitLab Project grain rather than a universal taxonomy.

Created At

Developer identifier: projects.created_atCreated At records timestamp when the project was created. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the Temporal.DateTime scalar.

Creator ID

Developer identifier: projects.creator_idCreator ID records user ID of the project creator. It is needed to refer to the same creator across records without relying on display text.

Enables: match creator_id to creator references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is an identifier, not a measured quantity.

Default Branch

Developer identifier: projects.default_branchDefault Branch records name of the default branch (e.g., main, master). It is needed to distinguish Projects rows by the exact GitLab-returned default branch value.

Enables: separate Projects rows by the exact GitLab-returned default_branch label when comparing default branch.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Description

Developer identifier: projects.descriptionDescription records project description text. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is description text at one GitLab Project record per row; this is only the content included in the GitLab response for this record.

Description HTML

Developer identifier: projects.description_htmlDescription HTML records HTML-rendered project description. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description_html and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is description text at one GitLab Project record per row; this is only the content included in the GitLab response for this record.

Emails Disabled

Developer identifier: projects.emails_disabledEmails Disabled records whether email notifications are disabled. It is needed to distinguish Projects rows by the exact GitLab-returned emails disabled value.

Enables: select Projects rows where emails_disabled is true or false when comparing the condition described by Emails Disabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Emails Enabled

Developer identifier: projects.emails_enabledEmails Enabled records whether email notifications are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned emails enabled value.

Enables: select Projects rows where emails_enabled is true or false when comparing the condition described by Emails Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Empty Repo

Developer identifier: projects.empty_repoEmpty Repo records whether the repository is empty (no commits). It is needed to distinguish Projects rows by the exact GitLab-returned empty repo value.

Enables: select Projects rows where empty_repo is true or false when comparing the condition described by Empty Repo.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Enforce Auth Checks On Uploads

Developer identifier: projects.enforce_auth_checks_on_uploadsEnforce Auth Checks On Uploads records whether authorization checks are enforced on file uploads. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact enforce_auth_checks_on_uploads access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Environments Access Level

Developer identifier: projects.environments_access_levelEnvironments Access Level records access level for environments. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact environments_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

External Authorization Classification Label

Developer identifier: projects.external_authorization_classification_labelExternal Authorization Classification Label records classification label used for external authorization. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact external_authorization_classification_label access value with the resource, account, or membership represented by the same Projects row.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Feature Flags Access Level

Developer identifier: projects.feature_flags_access_levelFeature Flags Access Level records access level for feature flags. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact feature_flags_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Forked From Project

Developer identifier: projects.forked_from_projectForked From Project records the project this was forked from, if applicable. It is needed to preserve the nested forked from project relationship or details on the parent GitLab Project record.

Enables: expand forked_from_project to connect the containing GitLab Project row to its returned forked from project entries.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one nested object per containing GitLab Project object when present.

Avatar URL

Developer identifier: projects.forked_from_project.avatar_urlAvatar URL records avatar URL of the upstream project. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is link at one GitLab Forked From Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Created At

Developer identifier: projects.forked_from_project.created_atCreated At records creation timestamp of the upstream project. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by created_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; the schema uses the Temporal.DateTime scalar.

Default Branch

Developer identifier: projects.forked_from_project.default_branchDefault Branch records default branch of the upstream project. It is needed to distinguish Projects rows by the exact GitLab-returned default branch value.

Enables: separate Projects rows by the exact GitLab-returned default_branch label when comparing default branch.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Description

Developer identifier: projects.forked_from_project.descriptionDescription records description of the upstream project. It is needed to inspect the exact description text included with this record.

Enables: inspect the description text returned in description and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is description text at one GitLab Forked From Project record per row; this is only the content included in the GitLab response for this record.

Forks Count

Developer identifier: projects.forked_from_project.forks_countForks Count records fork count of the upstream project. It is needed to measure the GitLab-reported number of forks at one GitLab Forked From Project record per row.

Enables: measure and compare the GitLab-reported number of forks in forks_count at one GitLab Forked From Project record per row.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is a GitLab-reported count at one GitLab Forked From Project record per row.

HTTP URL To Repo

Developer identifier: projects.forked_from_project.http_url_to_repoHTTP URL To Repo records HTTP clone URL of the upstream project. It is needed to reproduce the returned code or dependency configuration for this Projects record.

Enables: use http_url_to_repo to locate the configured source, package, or repository when reproducing the same job or repository setup.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: projects.forked_from_project.idID records ID of the upstream project. It is needed to refer to the same forked from project across records without relying on display text.

Enables: match id to forked from project references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is an identifier, not a measured quantity.

Last Activity At

Developer identifier: projects.forked_from_project.last_activity_atLast Activity At records last activity timestamp of the upstream project. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by last_activity_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; the schema uses the Temporal.DateTime scalar.

Name

Developer identifier: projects.forked_from_project.nameName records name of the upstream project. It is needed to compare the returned name for individual Projects rows and select rows with a specific name value.

Enables: locate Projects rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.

Name With Namespace

Developer identifier: projects.forked_from_project.name_with_namespaceName With Namespace records full name with namespace of the upstream project. It is needed to compare the returned name with namespace for individual Projects rows and select rows with a specific name_with_namespace value.

Enables: locate Projects rows whose returned name with namespace exactly matches name_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.

Namespace

Developer identifier: projects.forked_from_project.namespaceNamespace records namespace of the upstream project. It is needed to preserve the nested namespace relationship or details on the parent GitLab Forked From Project record.

Enables: expand namespace to connect the containing GitLab Forked From Project row to its returned namespace entries.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is one nested object per containing GitLab Forked From Project object when present.

Avatar URL

Developer identifier: projects.forked_from_project.namespace.avatar_urlAvatar URL records URL to the namespace avatar. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is link at one GitLab Namespace record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Full Path

Developer identifier: projects.forked_from_project.namespace.full_pathFull Path records full path of the namespace including parent groups. It is needed to compare the returned full path for individual Projects rows and select rows with a specific full_path value.

Enables: trace the full path relationship returned in full_path from the GitLab Namespace row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is interpreted at one GitLab Namespace record per row.

Developer identifier: projects.forked_from_project.namespace.idID records unique identifier for the namespace. It is needed to refer to the same namespace across records without relying on display text.

Enables: match id to namespace references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is an identifier, not a measured quantity.

Kind

Developer identifier: projects.forked_from_project.namespace.kindKind records kind of namespace (group or user). It is needed to distinguish Projects rows by the exact GitLab-returned kind value.

Enables: separate Projects rows by the exact GitLab-returned kind label when comparing kind.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is interpreted at one GitLab Namespace record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: projects.forked_from_project.namespace.nameName records name of the namespace. It is needed to compare the returned name for individual Projects rows and select rows with a specific name value.

Enables: locate Projects rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is interpreted at one GitLab Namespace record per row.

Parent ID

Developer identifier: projects.forked_from_project.namespace.parent_idParent ID records ID of the parent namespace, if any. It is needed to refer to the same parent across records without relying on display text.

Enables: match parent_id to parent references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is an identifier, not a measured quantity.

Path

Developer identifier: projects.forked_from_project.namespace.pathPath records URL-safe path of the namespace. It is needed to compare the returned path for individual Projects rows and select rows with a specific path value.

Enables: trace the path relationship returned in path from the GitLab Namespace row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is interpreted at one GitLab Namespace record per row.

Web URL

Developer identifier: projects.forked_from_project.namespace.web_urlWeb URL records web URL to the namespace. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Namespace object returned for Projects; it is link at one GitLab Namespace record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Path

Developer identifier: projects.forked_from_project.pathPath records path slug of the upstream project. It is needed to compare the returned path for individual Projects rows and select rows with a specific path value.

Enables: trace the path relationship returned in path from the GitLab Forked From Project row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.

Path With Namespace

Developer identifier: projects.forked_from_project.path_with_namespacePath With Namespace records full path with namespace of the upstream project. It is needed to compare the returned path with namespace for individual Projects rows and select rows with a specific path_with_namespace value.

Enables: locate Projects rows whose returned path with namespace exactly matches path_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row.

Readme URL

Developer identifier: projects.forked_from_project.readme_urlReadme URL records README URL of the upstream project. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by readme_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is link at one GitLab Forked From Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

SSH URL To Repo

Developer identifier: projects.forked_from_project.ssh_url_to_repoSSH URL To Repo records SSH clone URL of the upstream project. It is needed to reproduce the returned code or dependency configuration for this Projects record.

Enables: use ssh_url_to_repo to locate the configured source, package, or repository when reproducing the same job or repository setup.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is interpreted at one GitLab Forked From Project record per row; the returned link or template does not establish that the current credential can retrieve its target.

Star Count

Developer identifier: projects.forked_from_project.star_countStar Count records star count of the upstream project. It is needed to measure the GitLab-reported number of star at one GitLab Forked From Project record per row.

Enables: measure and compare the GitLab-reported number of star in star_count at one GitLab Forked From Project record per row.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is a GitLab-reported count at one GitLab Forked From Project record per row.

Topics

Developer identifier: projects.forked_from_project.topicsTopics records topics of the upstream project. It is needed to preserve the nested topics relationship or details on the parent GitLab Forked From Project record.

Enables: expand topics to connect the containing GitLab Forked From Project row to its returned topics entries.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is one returned collection per containing GitLab Forked From Project object.

Web URL

Developer identifier: projects.forked_from_project.web_urlWeb URL records web URL of the upstream project. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Forked From Project object returned for Projects; it is link at one GitLab Forked From Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Forking Access Level

Developer identifier: projects.forking_access_levelForking Access Level records access level for forking. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact forking_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Forks Count

Developer identifier: projects.forks_countForks Count records number of forks of this project. It is needed to measure the GitLab-reported number of forks of this project at one GitLab Project record per row.

Enables: measure and compare the GitLab-reported number of forks of this project in forks_count at one GitLab Project record per row.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is a GitLab-reported count at one GitLab Project record per row.

Group Runners Enabled

Developer identifier: projects.group_runners_enabledGroup Runners Enabled records whether group runners are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned group runners enabled value.

Enables: select Projects rows where group_runners_enabled is true or false when comparing the condition described by Group Runners Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

HTTP URL To Repo

Developer identifier: projects.http_url_to_repoHTTP URL To Repo records HTTP URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Projects record.

Enables: use http_url_to_repo to locate the configured source, package, or repository when reproducing the same job or repository setup.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: projects.idID records unique numeric identifier for the project. It is needed to distinguish repeated deliveries of the same Projects row using the declared ingestion key.

Enables: use id as the declared ingestion deduplication key for Projects and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Import Error

Developer identifier: projects.import_errorImport Error records error message from the project import. It is needed to inspect the exact error message included with this record.

Enables: inspect the error message returned in import_error and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is error message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.

Import Status

Developer identifier: projects.import_statusImport Status records status of the project import. It is needed to distinguish Projects rows by the exact GitLab-returned import status value.

Enables: separate Projects rows by the exact GitLab-returned import_status label when comparing import status.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Import Type

Developer identifier: projects.import_typeImport Type records type of import used to create the project. It is needed to distinguish Projects rows by the exact GitLab-returned import type value.

Enables: separate Projects rows by the exact GitLab-returned import_type label when comparing import type.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Import URL

Developer identifier: projects.import_urlImport URL records URL used to import the project. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by import_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is link at one GitLab Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Infrastructure Access Level

Developer identifier: projects.infrastructure_access_levelInfrastructure Access Level records access level for infrastructure. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact infrastructure_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Issue Branch Template

Developer identifier: projects.issue_branch_templateIssue Branch Template records custom template for issue branch names. It is needed to distinguish Projects rows by the exact GitLab-returned issue branch template value.

Enables: separate Projects rows by the exact GitLab-returned issue_branch_template label when comparing issue branch template.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Issues Access Level

Developer identifier: projects.issues_access_levelIssues Access Level records access level for issues. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact issues_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Issues Enabled

Developer identifier: projects.issues_enabledIssues Enabled records whether issues are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned issues enabled value.

Enables: select Projects rows where issues_enabled is true or false when comparing the condition described by Issues Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Jobs Enabled

Developer identifier: projects.jobs_enabledJobs Enabled records whether CI/CD jobs are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned jobs enabled value.

Enables: select Projects rows where jobs_enabled is true or false when comparing the condition described by Jobs Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Keep Latest Artifact

Developer identifier: projects.keep_latest_artifactKeep Latest Artifact records whether the latest artifact is kept. It is needed to distinguish Projects rows by the exact GitLab-returned keep latest artifact value.

Enables: select Projects rows where keep_latest_artifact is true or false when comparing the condition described by Keep Latest Artifact.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Last Activity At

Developer identifier: projects.last_activity_atLast Activity At records timestamp of the most recent activity on the project. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by last_activity_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the connector also declares it for record ordering; the schema assigns the metadata_timestamp semantic role; the schema uses the Temporal.DateTime scalar.

Lfs Enabled

Developer identifier: projects.lfs_enabledLfs Enabled records whether Git LFS is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned lfs enabled value.

Enables: select Projects rows where lfs_enabled is true or false when comparing the condition described by Lfs Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Marked For Deletion At

Developer identifier: projects.marked_for_deletion_atMarked For Deletion At records date when the project was marked for deletion. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by marked_for_deletion_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the Temporal.Date scalar.

Marked For Deletion On

Developer identifier: projects.marked_for_deletion_onMarked For Deletion On records date when the project was marked for deletion. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by marked_for_deletion_on, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the Temporal.Date scalar.

Merge Commit Template

Developer identifier: projects.merge_commit_templateMerge Commit Template records custom template for merge commit messages. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in merge_commit_template and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is commit message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.

Merge Method

Developer identifier: projects.merge_methodMerge Method records merge method used for the project. It is needed to distinguish Projects rows by the exact GitLab-returned merge method value.

Enables: separate Projects rows by the exact GitLab-returned merge_method label when comparing merge method.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Merge Pipelines Enabled

Developer identifier: projects.merge_pipelines_enabledMerge Pipelines Enabled records whether merged results pipelines are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned merge pipelines enabled value.

Enables: select Projects rows where merge_pipelines_enabled is true or false when comparing the condition described by Merge Pipelines Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Merge Requests Access Level

Developer identifier: projects.merge_requests_access_levelMerge Requests Access Level records access level for merge requests. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact merge_requests_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Merge Requests Enabled

Developer identifier: projects.merge_requests_enabledMerge Requests Enabled records whether merge requests are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned merge requests enabled value.

Enables: select Projects rows where merge_requests_enabled is true or false when comparing the condition described by Merge Requests Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Merge Trains Enabled

Developer identifier: projects.merge_trains_enabledMerge Trains Enabled records whether merge trains are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned merge trains enabled value.

Enables: select Projects rows where merge_trains_enabled is true or false when comparing the condition described by Merge Trains Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Mirror

Developer identifier: projects.mirrorMirror records whether the project is a mirror. It is needed to distinguish Projects rows by the exact GitLab-returned mirror value.

Enables: select Projects rows where mirror is true or false when comparing the condition described by Mirror.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Model Experiments Access Level

Developer identifier: projects.model_experiments_access_levelModel Experiments Access Level records access level for model experiments. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact model_experiments_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Model Registry Access Level

Developer identifier: projects.model_registry_access_levelModel Registry Access Level records access level for model registry. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact model_registry_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Monitor Access Level

Developer identifier: projects.monitor_access_levelMonitor Access Level records access level for monitoring. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact monitor_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Mr Default Target Self

Developer identifier: projects.mr_default_target_selfMr Default Target Self records whether MRs default to targeting the same project. It is needed to distinguish Projects rows by the exact GitLab-returned mr default target self value.

Enables: select Projects rows where mr_default_target_self is true or false when comparing the condition described by Mr Default Target Self.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: projects.nameName records human-readable project name. It is needed to compare the returned name for individual Projects rows and select rows with a specific name value.

Enables: locate Projects rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row.

Name With Namespace

Developer identifier: projects.name_with_namespaceName With Namespace records full name including namespace (e.g., ‘Group / Subgroup / Project’). It is needed to compare the returned name with namespace for individual Projects rows and select rows with a specific name_with_namespace value.

Enables: locate Projects rows whose returned name with namespace exactly matches name_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row.

Namespace

Developer identifier: projects.namespaceNamespace records the group/namespace this project belongs to. It is needed to preserve the nested namespace relationship or details on the parent GitLab Project record.

Enables: expand namespace to connect the containing GitLab Project row to its returned namespace entries.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one nested object per containing GitLab Project object when present.

Only Allow Merge If All Discussions Are Resolved

Developer identifier: projects.only_allow_merge_if_all_discussions_are_resolvedOnly Allow Merge If All Discussions Are Resolved records whether merges require all discussions to be resolved. It is needed to distinguish Projects rows by the exact GitLab-returned only allow merge if all discussions are resolved value.

Enables: select Projects rows where only_allow_merge_if_all_discussions_are_resolved is true or false when comparing the condition described by Only Allow Merge If All Discussions Are Resolved.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Only Allow Merge If Pipeline Succeeds

Developer identifier: projects.only_allow_merge_if_pipeline_succeedsOnly Allow Merge If Pipeline Succeeds records whether merges require a successful pipeline. It is needed to distinguish Projects rows by the exact GitLab-returned only allow merge if pipeline succeeds value.

Enables: select Projects rows where only_allow_merge_if_pipeline_succeeds is true or false when comparing the condition described by Only Allow Merge If Pipeline Succeeds.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Open Issues Count

Developer identifier: projects.open_issues_countOpen Issues Count records number of open issues in this project. It is needed to measure the GitLab-reported number of open issues in this project at one GitLab Project record per row.

Enables: measure and compare the GitLab-reported number of open issues in this project in open_issues_count at one GitLab Project record per row.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is a GitLab-reported count at one GitLab Project record per row.

Owner

Developer identifier: projects.ownerOwner records owner of the project (present for personal projects). It is needed to preserve the nested owner relationship or details on the parent GitLab Project record.

Enables: expand owner to connect the containing GitLab Project row to its returned owner entries.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one nested object per containing GitLab Project object when present.

Avatar URL

Developer identifier: projects.owner.avatar_urlAvatar URL records URL to the user avatar. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by avatar_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is link at one GitLab Owner record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Developer identifier: projects.owner.idID records unique identifier for the user. It is needed to refer to the same owner across records without relying on display text.

Enables: match id to owner references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is an identifier, not a measured quantity.

Locked

Developer identifier: projects.owner.lockedLocked records whether the user account is locked. It is needed to distinguish Projects rows by the exact GitLab-returned locked value.

Enables: select Projects rows where locked is true or false when comparing the condition described by Locked.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is interpreted at one GitLab Owner record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: projects.owner.nameName records display name of the owner. It is needed to attribute this Projects row to the returned person, account, or organization reference.

Enables: attribute the Projects row to the returned person or account and match the exact name value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is interpreted at one GitLab Owner record per row.

State

Developer identifier: projects.owner.stateState records account state (e.g., active, blocked). It is needed to distinguish Projects rows by the exact GitLab-returned state value.

Enables: separate Projects rows by the exact GitLab-returned state label when comparing state.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is interpreted at one GitLab Owner record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

User Name

Developer identifier: projects.owner.usernameUser Name records username of the owner. It is needed to attribute this Projects row to the returned person, account, or organization reference.

Enables: attribute the Projects row to the returned person or account and match the exact username value where it recurs in GitLab.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is interpreted at one GitLab Owner record per row.

Web URL

Developer identifier: projects.owner.web_urlWeb URL records web URL to the user profile. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Owner object returned for Projects; it is link at one GitLab Owner record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Packages Enabled

Developer identifier: projects.packages_enabledPackages Enabled records whether the package registry is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned packages enabled value.

Enables: select Projects rows where packages_enabled is true or false when comparing the condition described by Packages Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Pages Access Level

Developer identifier: projects.pages_access_levelPages Access Level records access level for GitLab Pages. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact pages_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Path

Developer identifier: projects.pathPath records URL-safe project path slug. It is needed to compare the returned path for individual Projects rows and select rows with a specific path value.

Enables: trace the path relationship returned in path from the GitLab Project row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row.

Path With Namespace

Developer identifier: projects.path_with_namespacePath With Namespace records full path including group namespace (e.g., group/subgroup/project). It is needed to compare the returned path with namespace for individual Projects rows and select rows with a specific path_with_namespace value.

Enables: locate Projects rows whose returned path with namespace exactly matches path_with_namespace and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row.

Permissions

Developer identifier: projects.permissionsPermissions records current user permissions on this project. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: expand permissions to examine the returned permissions details for the containing GitLab Project record.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one nested object per containing GitLab Project object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Group Access

Developer identifier: projects.permissions.group_accessGroup Access records access inherited from group membership. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: expand group_access to examine the returned group access details for the containing GitLab Permissions record.
Interpretation: GitLab reports this value on the GitLab Permissions object returned for Projects; it is one nested object per containing GitLab Permissions object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Access Level

Developer identifier: projects.permissions.group_access.access_levelAccess Level records numeric access level (10=Guest, 20=Reporter, 30=Developer, 40=Maintainer, 50=Owner). It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact access_level access value with the resource, account, or membership represented by the same Projects row.
Interpretation: GitLab reports this value on the GitLab Access Level object returned for Projects; it is interpreted at one GitLab Access Level record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Notification Level

Developer identifier: projects.permissions.group_access.notification_levelNotification Level records notification level setting. It is needed to compare the exact notification level configuration returned for this GitLab Access Level record.

Enables: compare the exact notification_level configuration returned for each GitLab Access Level record and select records with the configuration under review.
Interpretation: GitLab reports this value on the GitLab Access Level object returned for Projects; it is interpreted at one GitLab Access Level record per row.

Project Access

Developer identifier: projects.permissions.project_accessProject Access records direct project-level access. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: expand project_access to examine the returned project access details for the containing GitLab Permissions record.
Interpretation: GitLab reports this value on the GitLab Permissions object returned for Projects; it is one nested object per containing GitLab Permissions object when present; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Printing Merge Request Link Enabled

Developer identifier: projects.printing_merge_request_link_enabledPrinting Merge Request Link Enabled records whether the merge request link is printed after a push. It is needed to distinguish Projects rows by the exact GitLab-returned printing merge request link enabled value.

Enables: select Projects rows where printing_merge_request_link_enabled is true or false when comparing the condition described by Printing Merge Request Link Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Public Jobs

Developer identifier: projects.public_jobsPublic Jobs records whether CI/CD job logs are public. It is needed to distinguish Projects rows by the exact GitLab-returned public jobs value.

Enables: select Projects rows where public_jobs is true or false when comparing the condition described by Public Jobs.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Readme URL

Developer identifier: projects.readme_urlReadme URL records URL to the project README file. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by readme_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is link at one GitLab Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Releases Access Level

Developer identifier: projects.releases_access_levelReleases Access Level records access level for releases. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact releases_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Remove Source Branch After Merge

Developer identifier: projects.remove_source_branch_after_mergeRemove Source Branch After Merge records whether source branches are removed after merge. It is needed to distinguish Projects rows by the exact GitLab-returned remove source branch after merge value.

Enables: select Projects rows where remove_source_branch_after_merge is true or false when comparing the condition described by Remove Source Branch After Merge.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Repository Access Level

Developer identifier: projects.repository_access_levelRepository Access Level records access level for the repository. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact repository_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Repository Object Format

Developer identifier: projects.repository_object_formatRepository Object Format records object format of the repository (e.g., sha1, sha256). It is needed to distinguish Projects rows by the exact GitLab-returned repository object format value.

Enables: separate Projects rows by the exact GitLab-returned repository_object_format label when comparing repository object format.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Request Access Enabled

Developer identifier: projects.request_access_enabledRequest Access Enabled records whether users can request access to the project. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact request_access_enabled access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Requirements Access Level

Developer identifier: projects.requirements_access_levelRequirements Access Level records access level for the requirements feature. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact requirements_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Resolve Outdated Diff Discussions

Developer identifier: projects.resolve_outdated_diff_discussionsResolve Outdated Diff Discussions records whether outdated diff discussions are automatically resolved. It is needed to distinguish Projects rows by the exact GitLab-returned resolve outdated diff discussions value.

Enables: select Projects rows where resolve_outdated_diff_discussions is true or false when comparing the condition described by Resolve Outdated Diff Discussions.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Restrict User Defined Variables

Developer identifier: projects.restrict_user_defined_variablesRestrict User Defined Variables records whether user-defined CI/CD variables are restricted. It is needed to inspect the exact metadata included with this record.

Enables: inspect the exact metadata keys returned in restrict_user_defined_variables and associate them with the containing Projects record.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; keys and availability follow this GitLab response and may vary by object type or GitLab configuration; classification values are GitLab-returned labels rather than a universal taxonomy.

Runner Token Expiration Interval

Developer identifier: projects.runner_token_expiration_intervalRunner Token Expiration Interval records runner token expiration interval in seconds. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact runner_token_expiration_interval access value with the resource, account, or membership represented by the same Projects row.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; its unit or granularity is seconds; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Security And Compliance Access Level

Developer identifier: projects.security_and_compliance_access_levelSecurity And Compliance Access Level records access level for security and compliance features. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact security_and_compliance_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; a returned framework label or feature setting does not demonstrate that a framework requirement is satisfied; classification values are GitLab-returned labels rather than a universal taxonomy.

Security And Compliance Enabled

Developer identifier: projects.security_and_compliance_enabledSecurity And Compliance Enabled records whether the security and compliance features are enabled. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact security_and_compliance_enabled access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; a returned framework label or feature setting does not demonstrate that a framework requirement is satisfied; classification values are GitLab-returned labels rather than a universal taxonomy.

Service Desk Address

Developer identifier: projects.service_desk_addressService Desk Address records email address for the service desk. It is needed to preserve the GitLab-reported configured or derived address and place context for the same record.

Enables: compare the GitLab-reported configured or derived address and place context in service_desk_address for individual Projects rows without treating it as a verified physical location.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the Contact.Email scalar; the value is configured or derived address and place context; this GitLab-reported or configured context does not establish residency or verified physical presence.

Service Desk Enabled

Developer identifier: projects.service_desk_enabledService Desk Enabled records whether the service desk is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned service desk enabled value.

Enables: select Projects rows where service_desk_enabled is true or false when comparing the condition described by Service Desk Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Shared Runners Enabled

Developer identifier: projects.shared_runners_enabledShared Runners Enabled records whether shared runners are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned shared runners enabled value.

Enables: select Projects rows where shared_runners_enabled is true or false when comparing the condition described by Shared Runners Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Shared With Groups

Developer identifier: projects.shared_with_groupsShared With Groups records groups this project is shared with. It is needed to preserve the nested shared with groups relationship or details on the parent GitLab Project record.

Enables: expand shared_with_groups to connect the containing GitLab Project row to its returned shared with groups entries.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object.

Expires At

Developer identifier: projects.shared_with_groups.expires_atExpires At records expiration date of the share. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by expires_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Shared Group object returned for Projects; it is interpreted at one GitLab Shared Group record per row; the schema uses the Temporal.Date scalar.

Group Access Level

Developer identifier: projects.shared_with_groups.group_access_levelGroup Access Level records access level granted to the shared group. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: correlate the exact group_access_level access value with the resource, account, or membership represented by the same Projects row.
Interpretation: GitLab reports this value on the GitLab Shared Group object returned for Projects; it is interpreted at one GitLab Shared Group record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented.

Group Full Path

Developer identifier: projects.shared_with_groups.group_full_pathGroup Full Path records full path of the shared group. It is needed to compare the returned group full path for individual Projects rows and select rows with a specific group_full_path value.

Enables: trace the group full path relationship returned in group_full_path from the GitLab Shared Group row to its named GitLab context.
Interpretation: GitLab reports this value on the GitLab Shared Group object returned for Projects; it is interpreted at one GitLab Shared Group record per row.

Group ID

Developer identifier: projects.shared_with_groups.group_idGroup ID records ID of the shared group. It is needed to distinguish repeated deliveries of the same Projects row using the declared ingestion key.

Enables: use group_id as the declared ingestion deduplication key for Projects and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Shared Group object returned for Projects; it is an identifier, not a measured quantity; the connector declares it as an ingestion deduplication key.

Group Name

Developer identifier: projects.shared_with_groups.group_nameGroup Name records name of the shared group. It is needed to compare the returned group name for individual Projects rows and select rows with a specific group_name value.

Enables: locate Projects rows whose returned group name exactly matches group_name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Shared Group object returned for Projects; it is interpreted at one GitLab Shared Group record per row.

Snippets Access Level

Developer identifier: projects.snippets_access_levelSnippets Access Level records access level for snippets. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact snippets_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Snippets Enabled

Developer identifier: projects.snippets_enabledSnippets Enabled records whether snippets are enabled. It is needed to distinguish Projects rows by the exact GitLab-returned snippets enabled value.

Enables: select Projects rows where snippets_enabled is true or false when comparing the condition described by Snippets Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Squash Commit Template

Developer identifier: projects.squash_commit_templateSquash Commit Template records custom template for squash commit messages. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in squash_commit_template and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is commit message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.

Squash Option

Developer identifier: projects.squash_optionSquash Option records squash option for merge requests. It is needed to distinguish Projects rows by the exact GitLab-returned squash option value.

Enables: separate Projects rows by the exact GitLab-returned squash_option label when comparing squash option.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

SSH URL To Repo

Developer identifier: projects.ssh_url_to_repoSSH URL To Repo records SSH URL for cloning the repository. It is needed to reproduce the returned code or dependency configuration for this Projects record.

Enables: use ssh_url_to_repo to locate the configured source, package, or repository when reproducing the same job or repository setup.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the returned link or template does not establish that the current credential can retrieve its target.

Star Count

Developer identifier: projects.star_countStar Count records number of stars on this project. It is needed to measure the GitLab-reported number of stars on this project at one GitLab Project record per row.

Enables: measure and compare the GitLab-reported number of stars on this project in star_count at one GitLab Project record per row.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is a GitLab-reported count at one GitLab Project record per row.

Statistics

Developer identifier: projects.statisticsStatistics records project storage and usage statistics. It is needed to preserve the nested statistics relationship or details on the parent GitLab Project record.

Enables: expand statistics to connect the containing GitLab Project row to its returned statistics entries.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one nested object per containing GitLab Project object when present.

Commit Count

Developer identifier: projects.statistics.commit_countCommit Count records total number of commits. It is needed to measure the GitLab-reported number of commits at one GitLab Project Statistics record per row.

Enables: measure and compare the GitLab-reported number of commits in commit_count at one GitLab Project Statistics record per row.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; it is a GitLab-reported count at one GitLab Project Statistics record per row.

Container Registry Size

Developer identifier: projects.statistics.container_registry_sizeContainer Registry Size records container registry size in bytes. It is needed to measure the reported container registry size for one gitlab project statistics record.

Enables: measure and compare container_registry_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Job Artifacts Size

Developer identifier: projects.statistics.job_artifacts_sizeJob Artifacts Size records job artifacts size in bytes. It is needed to measure the reported job artifacts size for one gitlab project statistics record.

Enables: measure and compare job_artifacts_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Lfs Objects Size

Developer identifier: projects.statistics.lfs_objects_sizeLfs Objects Size records LFS objects size in bytes. It is needed to measure the reported lfs objects size for one gitlab project statistics record.

Enables: measure and compare lfs_objects_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Packages Size

Developer identifier: projects.statistics.packages_sizePackages Size records packages size in bytes. It is needed to measure the reported packages size for one gitlab project statistics record.

Enables: measure and compare packages_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Pipeline Artifacts Size

Developer identifier: projects.statistics.pipeline_artifacts_sizePipeline Artifacts Size records pipeline artifacts size in bytes. It is needed to measure the reported pipeline artifacts size for one gitlab project statistics record.

Enables: measure and compare pipeline_artifacts_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Repository Size

Developer identifier: projects.statistics.repository_sizeRepository Size records repository size in bytes. It is needed to measure the reported repository size for one gitlab project statistics record.

Enables: measure and compare repository_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Snippets Size

Developer identifier: projects.statistics.snippets_sizeSnippets Size records snippets size in bytes. It is needed to measure the reported snippets size for one gitlab project statistics record.

Enables: measure and compare snippets_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Storage Size

Developer identifier: projects.statistics.storage_sizeStorage Size records total storage size in bytes. It is needed to measure the reported storage size for one gitlab project statistics record.

Enables: measure and compare storage_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Uploads Size

Developer identifier: projects.statistics.uploads_sizeUploads Size records uploads size in bytes. It is needed to measure the reported uploads size for one gitlab project statistics record.

Enables: measure and compare uploads_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Wiki Size

Developer identifier: projects.statistics.wiki_sizeWiki Size records wiki size in bytes. It is needed to measure the reported wiki size for one gitlab project statistics record.

Enables: measure and compare wiki_size per GitLab Project Statistics record in bytes.
Interpretation: GitLab reports this value on the GitLab Project Statistics object returned for Projects; its unit or granularity is bytes.

Suggestion Commit Message

Developer identifier: projects.suggestion_commit_messageSuggestion Commit Message records custom commit message template for suggestions. It is needed to inspect the exact commit message included with this record.

Enables: inspect the commit message returned in suggestion_commit_message and attribute it to the same record’s repository or project, owner, and update time where returned.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is commit message at one GitLab Project record per row; this is only the content included in the GitLab response for this record.

Topics

Developer identifier: projects.topicsTopics records array of topic tags assigned to the project. It is needed to preserve the nested topics relationship or details on the parent GitLab Project record.

Enables: expand topics to connect the containing GitLab Project row to its returned topics entries.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is one returned collection per containing GitLab Project object.

Updated At

Developer identifier: projects.updated_atUpdated At records timestamp when the project was last updated. It is needed to place the record at the time or date reported for this event or state.

Enables: bound Projects records by updated_at, order their returned events or state changes, and correlate records reported at the same time.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; the schema uses the Temporal.DateTime scalar.

Visibility

Developer identifier: projects.visibilityVisibility records project visibility level. It is needed to distinguish Projects rows by the exact GitLab-returned visibility value.

Enables: separate Projects rows by the exact GitLab-returned visibility label when comparing visibility.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Warn About Potentially Unwanted Characters

Developer identifier: projects.warn_about_potentially_unwanted_charactersWarn About Potentially Unwanted Characters records whether warnings about potentially unwanted characters are shown. It is needed to distinguish Projects rows by the exact GitLab-returned warn about potentially unwanted characters value.

Enables: select Projects rows where warn_about_potentially_unwanted_characters is true or false when comparing the condition described by Warn About Potentially Unwanted Characters.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Web URL

Developer identifier: projects.web_urlWeb URL records web URL to the project in the GitLab UI. It is needed to inspect the exact link included with this record.

Enables: open or correlate the exact GitLab resource referenced by web_url while retaining the containing Projects record as provenance.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is link at one GitLab Project record per row; the schema uses the Network.Url scalar; the returned link or template does not establish that the current credential can retrieve its target.

Wiki Access Level

Developer identifier: projects.wiki_access_levelWiki Access Level records access level for the wiki. It is needed to correlate the returned access or audit evidence with the subject and action represented by the same record.

Enables: select Projects rows with the exact wiki_access_level access-related value being investigated.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; use it for investigation and evidence correlation; it does not prove that all activity or access is represented; classification values are GitLab-returned labels rather than a universal taxonomy.

Wiki Enabled

Developer identifier: projects.wiki_enabledWiki Enabled records whether the wiki is enabled. It is needed to distinguish Projects rows by the exact GitLab-returned wiki enabled value.

Enables: select Projects rows where wiki_enabled is true or false when comparing the condition described by Wiki Enabled.
Interpretation: GitLab reports this value on the GitLab Project object returned for Projects; it is interpreted at one GitLab Project record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Repository Files

Developer identifier: reposRepository Files covers project repository file tree.

Enables: inventory returned repositories or project files and correlate each record with its owner, namespace, visibility, default branch, and update time where present.
Scope: Project repository file tree; the connector reads /api/v4/projects/{id}/repository/tree as a snapshot stream in full mode. The configured credential must grant the declared read_api access scope; records outside that access are not returned. A successful full collection can reveal a previously returned row as absent, but a credential or permission change can produce the same observation.

Developer identifier: repos.idID records SHA-1 hash identifier of the tree entry (blob or tree object id). It is needed to refer to the same repo tree entry across records without relying on display text.

Enables: match id to repo tree entry references carrying the same GitLab-issued value in related GitLab records.
Interpretation: GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is an identifier, not a measured quantity.

Mode

Developer identifier: repos.modeMode records unix file mode string (e.g. ‘100644’ for a regular file, ‘040000’ for a directory). It is needed to distinguish Repository Files rows by the exact GitLab-returned mode value.

Enables: separate Repository Files rows by the exact GitLab-returned mode label when comparing mode.
Interpretation: GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is interpreted at one GitLab Repo Tree Entry record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Name

Developer identifier: repos.nameName records file or directory name (last path segment). It is needed to compare the returned name for individual Repository Files rows and select rows with a specific name value.

Enables: locate Repository Files rows whose returned name exactly matches name and retain the GitLab identifier for any cross-record match.
Interpretation: GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is interpreted at one GitLab Repo Tree Entry record per row.

Path

Developer identifier: repos.pathPath records full path of the entry from the repository root. It is needed to distinguish repeated deliveries of the same Repository Files row using the declared ingestion key.

Enables: use path as the declared ingestion deduplication key for Repository Files and match repeated rows carrying the same GitLab identifier.
Interpretation: GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is interpreted at one GitLab Repo Tree Entry record per row; the connector declares it as an ingestion deduplication key; the schema uses the Asset.FilePath scalar.

Type

Developer identifier: repos.typeType records entry type: ‘tree’ for a directory, ‘blob’ for a file. It is needed to distinguish Repository Files rows by the exact GitLab-returned type value.

Enables: separate Repository Files rows by the exact GitLab-returned type label when comparing type.
Interpretation: GitLab reports this value on the GitLab Repo Tree Entry object returned for Repository Files; it is interpreted at one GitLab Repo Tree Entry record per row; classification values are GitLab-returned labels rather than a universal taxonomy.

Error	Meaning	Solution
`401 Unauthorized`	Invalid token	Verify token is correct and not expired
`403 Forbidden`	Insufficient scope	Add required scope and regenerate
`404 Not Found`	No access to resource	Check user has project/group membership
`429 Rate Limited`	Too many requests	Implement backoff

Common Issues

Token expired

GitLab PATs have expiration dates. Generate a new token with a longer expiration.

Can’t access group projects

Ensure your GitLab user has at least Reporter access to the group.GitLab API — Official API documentationToken Types — Access token guide

​Code & MRs

​Issues & Planning

​Data streams

​GitLab

​What You’ll Need

​Step 1: Access User Settings

​Step 2: Create Personal Access Token

​Step 3: Select Scopes

​Step 4: Create and Copy Token

​Step 5: Enter values in the form

​Common Issues

​Token expired

​Can’t access group projects

Code & MRs

Issues & Planning

Data streams

GitLab

What You’ll Need

Step 1: Access User Settings

Step 2: Create Personal Access Token

Step 3: Select Scopes

Step 4: Create and Copy Token

Step 5: Enter values in the form

Common Issues

Token expired

Can’t access group projects