# GraphQL API Resources
> 原文:[https://docs.gitlab.com/ee/api/graphql/reference/](https://docs.gitlab.com/ee/api/graphql/reference/)
* [AccessLevel](#accesslevel)
* [AddAwardEmojiPayload](#addawardemojipayload)
* [AddProjectToSecurityDashboardPayload](#addprojecttosecuritydashboardpayload)
* [AdminSidekiqQueuesDeleteJobsPayload](#adminsidekiqqueuesdeletejobspayload)
* [AlertManagementAlert](#alertmanagementalert)
* [AlertManagementAlertStatusCountsType](#alertmanagementalertstatuscountstype)
* [AlertSetAssigneesPayload](#alertsetassigneespayload)
* [AlertTodoCreatePayload](#alerttodocreatepayload)
* [AwardEmoji](#awardemoji)
* [AwardEmojiAddPayload](#awardemojiaddpayload)
* [AwardEmojiRemovePayload](#awardemojiremovepayload)
* [AwardEmojiTogglePayload](#awardemojitogglepayload)
* [BaseService](#baseservice)
* [Blob](#blob)
* [Board](#board)
* [BoardList](#boardlist)
* [BoardListUpdateLimitMetricsPayload](#boardlistupdatelimitmetricspayload)
* [Branch](#branch)
* [Commit](#commit)
* [CommitCreatePayload](#commitcreatepayload)
* [ComplianceFramework](#complianceframework)
* [ContainerExpirationPolicy](#containerexpirationpolicy)
* [CreateAlertIssuePayload](#createalertissuepayload)
* [CreateAnnotationPayload](#createannotationpayload)
* [CreateBranchPayload](#createbranchpayload)
* [CreateDiffNotePayload](#creatediffnotepayload)
* [CreateEpicPayload](#createepicpayload)
* [CreateImageDiffNotePayload](#createimagediffnotepayload)
* [CreateIterationPayload](#createiterationpayload)
* [CreateNotePayload](#createnotepayload)
* [CreateRequirementPayload](#createrequirementpayload)
* [CreateSnippetPayload](#createsnippetpayload)
* [DastSiteProfileCreatePayload](#dastsiteprofilecreatepayload)
* [DeleteAnnotationPayload](#deleteannotationpayload)
* [DeleteJobsResponse](#deletejobsresponse)
* [Design](#design)
* [DesignAtVersion](#designatversion)
* [DesignCollection](#designcollection)
* [DesignManagement](#designmanagement)
* [DesignManagementDeletePayload](#designmanagementdeletepayload)
* [DesignManagementUploadPayload](#designmanagementuploadpayload)
* [DesignVersion](#designversion)
* [DestroyNotePayload](#destroynotepayload)
* [DestroySnippetPayload](#destroysnippetpayload)
* [DetailedStatus](#detailedstatus)
* [DiffPosition](#diffposition)
* [DiffRefs](#diffrefs)
* [DiffStats](#diffstats)
* [DiffStatsSummary](#diffstatssummary)
* [Discussion](#discussion)
* [DiscussionToggleResolvePayload](#discussiontoggleresolvepayload)
* [DismissVulnerabilityPayload](#dismissvulnerabilitypayload)
* [Environment](#environment)
* [Epic](#epic)
* [EpicAddIssuePayload](#epicaddissuepayload)
* [EpicDescendantCount](#epicdescendantcount)
* [EpicDescendantWeights](#epicdescendantweights)
* [EpicHealthStatus](#epichealthstatus)
* [EpicIssue](#epicissue)
* [EpicPermissions](#epicpermissions)
* [EpicSetSubscriptionPayload](#epicsetsubscriptionpayload)
* [EpicTreeReorderPayload](#epictreereorderpayload)
* [GeoNode](#geonode)
* [GrafanaIntegration](#grafanaintegration)
* [Group](#group)
* [GroupMember](#groupmember)
* [GroupPermissions](#grouppermissions)
* [Issue](#issue)
* [IssuePermissions](#issuepermissions)
* [IssueSetConfidentialPayload](#issuesetconfidentialpayload)
* [IssueSetDueDatePayload](#issuesetduedatepayload)
* [IssueSetIterationPayload](#issuesetiterationpayload)
* [IssueSetLockedPayload](#issuesetlockedpayload)
* [IssueSetWeightPayload](#issuesetweightpayload)
* [Iteration](#iteration)
* [JiraImport](#jiraimport)
* [JiraImportStartPayload](#jiraimportstartpayload)
* [JiraImportUsersPayload](#jiraimportuserspayload)
* [JiraProject](#jiraproject)
* [JiraService](#jiraservice)
* [JiraUser](#jirauser)
* [Label](#label)
* [MarkAsSpamSnippetPayload](#markasspamsnippetpayload)
* [MergeRequest](#mergerequest)
* [MergeRequestCreatePayload](#mergerequestcreatepayload)
* [MergeRequestPermissions](#mergerequestpermissions)
* [MergeRequestSetAssigneesPayload](#mergerequestsetassigneespayload)
* [MergeRequestSetLabelsPayload](#mergerequestsetlabelspayload)
* [MergeRequestSetLockedPayload](#mergerequestsetlockedpayload)
* [MergeRequestSetMilestonePayload](#mergerequestsetmilestonepayload)
* [MergeRequestSetSubscriptionPayload](#mergerequestsetsubscriptionpayload)
* [MergeRequestSetWipPayload](#mergerequestsetwippayload)
* [MergeRequestUpdatePayload](#mergerequestupdatepayload)
* [Metadata](#metadata)
* [MetricsDashboard](#metricsdashboard)
* [MetricsDashboardAnnotation](#metricsdashboardannotation)
* [Milestone](#milestone)
* [MilestoneStats](#milestonestats)
* [Namespace](#namespace)
* [Note](#note)
* [NotePermissions](#notepermissions)
* [Package](#package)
* [PackageFileRegistry](#packagefileregistry)
* [PageInfo](#pageinfo)
* [Pipeline](#pipeline)
* [PipelinePermissions](#pipelinepermissions)
* [Project](#project)
* [ProjectMember](#projectmember)
* [ProjectPermissions](#projectpermissions)
* [ProjectStatistics](#projectstatistics)
* [Release](#release)
* [ReleaseAssetLink](#releaseassetlink)
* [ReleaseAssets](#releaseassets)
* [ReleaseEvidence](#releaseevidence)
* [ReleaseLinks](#releaselinks)
* [ReleaseSource](#releasesource)
* [RemoveAwardEmojiPayload](#removeawardemojipayload)
* [RemoveProjectFromSecurityDashboardPayload](#removeprojectfromsecuritydashboardpayload)
* [Repository](#repository)
* [Requirement](#requirement)
* [RequirementPermissions](#requirementpermissions)
* [RequirementStatesCount](#requirementstatescount)
* [RootStorageStatistics](#rootstoragestatistics)
* [RunDASTScanPayload](#rundastscanpayload)
* [SastCiConfigurationAnalyzersEntity](#sastciconfigurationanalyzersentity)
* [SastCiConfigurationEntity](#sastciconfigurationentity)
* [SastCiConfigurationOptionsEntity](#sastciconfigurationoptionsentity)
* [ScannedResource](#scannedresource)
* [SecurityReportSummary](#securityreportsummary)
* [SecurityReportSummarySection](#securityreportsummarysection)
* [SecurityScanners](#securityscanners)
* [SentryDetailedError](#sentrydetailederror)
* [SentryError](#sentryerror)
* [SentryErrorCollection](#sentryerrorcollection)
* [SentryErrorFrequency](#sentryerrorfrequency)
* [SentryErrorStackTrace](#sentryerrorstacktrace)
* [SentryErrorStackTraceContext](#sentryerrorstacktracecontext)
* [SentryErrorStackTraceEntry](#sentryerrorstacktraceentry)
* [SentryErrorTags](#sentryerrortags)
* [Snippet](#snippet)
* [SnippetBlob](#snippetblob)
* [SnippetBlobViewer](#snippetblobviewer)
* [SnippetPermissions](#snippetpermissions)
* [Submodule](#submodule)
* [TaskCompletionStatus](#taskcompletionstatus)
* [TestReport](#testreport)
* [Timelog](#timelog)
* [Todo](#todo)
* [TodoMarkDonePayload](#todomarkdonepayload)
* [TodoRestoreManyPayload](#todorestoremanypayload)
* [TodoRestorePayload](#todorestorepayload)
* [TodosMarkAllDonePayload](#todosmarkalldonepayload)
* [ToggleAwardEmojiPayload](#toggleawardemojipayload)
* [Tree](#tree)
* [TreeEntry](#treeentry)
* [UpdateAlertStatusPayload](#updatealertstatuspayload)
* [UpdateContainerExpirationPolicyPayload](#updatecontainerexpirationpolicypayload)
* [UpdateEpicPayload](#updateepicpayload)
* [UpdateImageDiffNotePayload](#updateimagediffnotepayload)
* [UpdateIssuePayload](#updateissuepayload)
* [UpdateIterationPayload](#updateiterationpayload)
* [UpdateNotePayload](#updatenotepayload)
* [UpdateRequirementPayload](#updaterequirementpayload)
* [UpdateSnippetPayload](#updatesnippetpayload)
* [User](#user)
* [UserPermissions](#userpermissions)
* [VulnerabilitiesCountByDayAndSeverity](#vulnerabilitiescountbydayandseverity)
* [Vulnerability](#vulnerability)
* [VulnerabilityIdentifier](#vulnerabilityidentifier)
* [VulnerabilityIssueLink](#vulnerabilityissuelink)
* [VulnerabilityLocationContainerScanning](#vulnerabilitylocationcontainerscanning)
* [VulnerabilityLocationDast](#vulnerabilitylocationdast)
* [VulnerabilityLocationDependencyScanning](#vulnerabilitylocationdependencyscanning)
* [VulnerabilityLocationSast](#vulnerabilitylocationsast)
* [VulnerabilityLocationSecretDetection](#vulnerabilitylocationsecretdetection)
* [VulnerabilityPermissions](#vulnerabilitypermissions)
* [VulnerabilityScanner](#vulnerabilityscanner)
* [VulnerabilitySeveritiesCount](#vulnerabilityseveritiescount)
* [VulnerableDependency](#vulnerabledependency)
* [VulnerablePackage](#vulnerablepackage)
# GraphQL API Resources[](#graphql-api-resources "Permalink")
本文档是基于 GitLab 当前的 GraphQL 模式自行生成的.
可以使用[GraphiQL IDE](../index.html#graphiql)交互式地探索该 API.
下表每个都记录了 GraphQL 类型. 类型可以轻松地与模型匹配,但是并非所有的字段和方法都可以通过 GraphQL 获得.
**警告:**不推荐使用的字段标有 .
## AccessLevel[](#accesslevel "Permalink")
表示用户与之相关的对象之间的关系的访问级别
| Name | Type | Description |
| --- | --- | --- |
| `integerValue` | Int | 访问级别的整数表示 |
| `stringValue` | AccessLevelEnum | 访问级别的字符串表示形式 |
## AddAwardEmojiPayload[](#addawardemojipayload "Permalink")
自动生成的 AddAwardEmoji 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `awardEmoji` | AwardEmoji | 突变后的奖励表情符号 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## AddProjectToSecurityDashboardPayload[](#addprojecttosecuritydashboardpayload "Permalink")
自动生成的 AddProjectToSecurityDashboard 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `project` | Project | 添加到 Instance Security 仪表盘的项目 |
## AdminSidekiqQueuesDeleteJobsPayload[](#adminsidekiqqueuesdeletejobspayload "Permalink")
自动生成的 AdminSidekiqQueuesDeleteJobs 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `result` | DeleteJobsResponse | 有关删除请求状态的信息 |
## AlertManagementAlert[](#alertmanagementalert "Permalink")
描述来自项目警报管理的警报
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time | 创建警报的时间戳 |
| `description` | String | 警报说明 |
| `details` | JSON | 警报详细信息 |
| `endedAt` | Time | 警报结束的时间戳记 |
| `eventCount` | Int | 此警报的事件数 |
| `hosts` | 串! =>数组 | 警报来自的主机列表 |
| `iid` | ID! | 警报的内部 ID |
| `issueIid` | ID | 警报附带的 GitLab 问题的内部 ID |
| `metricsDashboardUrl` | String | 嵌入警报的指标的 URL |
| `monitoringTool` | String | 警报来自的监视工具 |
| `service` | String | 服务警报来自 |
| `severity` | AlertManagementSeverity | 警报的严重程度 |
| `startedAt` | Time | 发出警报的时间戳记 |
| `status` | AlertManagementStatus | 警报状态 |
| `title` | String | 警报标题 |
| `updatedAt` | Time | 警报的时间戳记最新更新 |
## AlertManagementAlertStatusCountsType[](#alertmanagementalertstatuscountstype "Permalink")
代表所代表类别的警报总数
| Name | Type | Description |
| --- | --- | --- |
| `acknowledged` | Int | 项目状态为 ACKNOWLEDGED 的警报数 |
| `all` | Int | 项目警报总数 |
| `ignored` | Int | 项目状态为 IGNORED 的警报数 |
| `open` | Int | 项目状态为 TRIGGERED 或 ACKNOWLEDGED 的警报数 |
| `resolved` | Int | 项目状态为"已解决"的警报数 |
| `triggered` | Int | 项目状态为 TRIGGERED 的警报数 |
## AlertSetAssigneesPayload[](#alertsetassigneespayload "Permalink")
自动生成的 AlertSetAssignees 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `alert` | AlertManagementAlert | 突变后的警报 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后产生的问题 |
| `todo` | Todo | 突变后的待办事项 |
## AlertTodoCreatePayload[](#alerttodocreatepayload "Permalink")
自动生成的 AlertTodoCreate 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `alert` | AlertManagementAlert | 突变后的警报 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后产生的问题 |
| `todo` | Todo | 突变后的待办事项 |
## AwardEmoji[](#awardemoji "Permalink")
用户授予的表情符号.
| Name | Type | Description |
| --- | --- | --- |
| `description` | String! | 表情符号说明 |
| `emoji` | String! | 表情符号作为图标 |
| `name` | String! | 表情符号名称 |
| `unicode` | String! | Unicode 中的表情符号 |
| `unicodeVersion` | String! | 此表情符号的 unicode 版本 |
| `user` | User! | 授予表情符号的用户 |
## AwardEmojiAddPayload[](#awardemojiaddpayload "Permalink")
自动生成的 AwardEmojiAdd 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `awardEmoji` | AwardEmoji | 突变后的奖励表情符号 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## AwardEmojiRemovePayload[](#awardemojiremovepayload "Permalink")
自动生成的 AwardEmoji 退货类型
| Name | Type | Description |
| --- | --- | --- |
| `awardEmoji` | AwardEmoji | The award emoji after mutation |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## AwardEmojiTogglePayload[](#awardemojitogglepayload "Permalink")
自动生成的 AwardEmojiToggle 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `awardEmoji` | AwardEmoji | 突变后的奖励表情符号 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `toggledOn` | Boolean! | 指示表情符号的状态. 如果切换开关授予表情符号,则为 true;如果切换开关删除了表情符号,则为 false. |
## BaseService[](#baseservice "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `active` | Boolean | 指示服务是否处于活动状态 |
| `type` | String | 服务的类别名称 |
## Blob[](#blob "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `flatPath` | String! | 条目的平坦路径 |
| `id` | ID! | 条目 ID |
| `lfsOid` | String | Blob 的 LFS ID |
| `mode` | String | 数字格式的 Blob 模式 |
| `name` | String! | 条目名称 |
| `path` | String! | 条目路径 |
| `sha` | String! | 提交的最后提交 sha |
| `type` | EntryType! | 树条目的类型 |
| `webUrl` | String | Blob 的网址 |
## Board[](#board "Permalink")
代表一个项目或小组委员会
| Name | Type | Description |
| --- | --- | --- |
| `id` | ID! | 单板的 ID(全局 ID) |
| `name` | String | 董事会名称 |
| `weight` | Int | 木板重量 |
## BoardList[](#boardlist "Permalink")
代表发行板的列表
| Name | Type | Description |
| --- | --- | --- |
| `assignee` | User | 列表中的受让人 |
| `collapsed` | Boolean | 指示此用户的列表是否折叠 |
| `id` | ID! | 列表的 ID(全局 ID) |
| `label` | Label | 清单标签 |
| `limitMetric` | ListLimitMetric | 列表的当前限制指标 |
| `listType` | String! | 清单类型 |
| `maxIssueCount` | Int | 列表中的最大问题数 |
| `maxIssueWeight` | Int | 清单中的最大问题权重 |
| `milestone` | Milestone | 名单的里程碑 |
| `position` | Int | 名单在董事会中的位置 |
| `title` | String! | 清单标题 |
## BoardListUpdateLimitMetricsPayload[](#boardlistupdatelimitmetricspayload "Permalink")
自动生成的 BoardListUpdateLimitMetrics 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `list` | BoardList | 更新清单 |
## Branch[](#branch "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `commit` | Commit | 提交分支 |
| `name` | String! | 分行名称 |
## Commit[](#commit "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `author` | User | 提交的作者 |
| `authorGravatar` | String | 提交作者 |
| `authorName` | String | 提交作者姓名 |
| `authoredDate` | Time | 提交提交的时间戳 |
| `description` | String | 提交消息的描述 |
| `id` | ID! | 提交的 ID(全局 ID) |
| `latestPipeline` | Pipeline | **不推荐使用:**使用`pipelines` . 在 12.5 中弃用 |
| `message` | String | 原始提交消息 |
| `sha` | String! | 提交的 SHA1 ID |
| `signatureHtml` | String | 提交签名的 HTML |
| `title` | String | 提交消息的标题 |
| `titleHtml` | String | GitLab 风味 Markdown `title`渲染 |
| `webUrl` | String! | 提交的 Web URL |
## CommitCreatePayload[](#commitcreatepayload "Permalink")
自动生成的 CommitCreate 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `commit` | Commit | 突变后的提交 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## ComplianceFramework[](#complianceframework "Permalink")
表示与项目关联的 ComplianceFramework
| Name | Type | Description |
| --- | --- | --- |
| `name` | ProjectSettingEnum! | 合规框架名称 |
## ContainerExpirationPolicy[](#containerexpirationpolicy "Permalink")
标签过期策略旨在仅保留最重要的图像
| Name | Type | Description |
| --- | --- | --- |
| `cadence` | ContainerExpirationPolicyCadenceEnum! | 该容器到期政策时间表 |
| `createdAt` | Time! | 创建容器到期策略的时间戳 |
| `enabled` | Boolean! | 指示是否启用了此容器过期策略 |
| `keepN` | ContainerExpirationPolicyKeepEnum | 要保留的标签数 |
| `nameRegex` | UntrustedRegexp | 名称与此正则表达式模式匹配的标签将过期 |
| `nameRegexKeep` | UntrustedRegexp | 名称与该正则表达式模式匹配的标签将被保留 |
| `nextRunAt` | Time | 下次该容器到期策略将被执行 |
| `olderThan` | ContainerExpirationPolicyOlderThanEnum | Tags older that this will expire |
| `updatedAt` | Time! | 容器过期策略更新的时间戳 |
## CreateAlertIssuePayload[](#createalertissuepayload "Permalink")
自动生成的 CreateAlertIssue 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `alert` | AlertManagementAlert | 突变后的警报 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后产生的问题 |
| `todo` | Todo | 突变后的待办事项 |
## CreateAnnotationPayload[](#createannotationpayload "Permalink")
自动生成的 CreateAnnotation 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `annotation` | MetricsDashboardAnnotation | 创建的注释 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## CreateBranchPayload[](#createbranchpayload "Permalink")
自动生成的 CreateBranch 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `branch` | Branch | 突变后分支 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## CreateDiffNotePayload[](#creatediffnotepayload "Permalink")
自动生成的 CreateDiffNote 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `note` | Note | 突变后的音符 |
## CreateEpicPayload[](#createepicpayload "Permalink")
自动生成的 CreateEpic 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `epic` | Epic | 创造的史诗 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## CreateImageDiffNotePayload[](#createimagediffnotepayload "Permalink")
自动生成的 CreateImageDiffNote 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `note` | Note | 突变后的音符 |
## CreateIterationPayload[](#createiterationpayload "Permalink")
自动生成的 CreateIteration 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `iteration` | Iteration | 创建的迭代 |
## CreateNotePayload[](#createnotepayload "Permalink")
自动生成的 CreateNote 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `note` | Note | 突变后的音符 |
## CreateRequirementPayload[](#createrequirementpayload "Permalink")
自动生成的 CreateRequirement 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `requirement` | Requirement | 突变后的要求 |
## CreateSnippetPayload[](#createsnippetpayload "Permalink")
自动生成的 CreateSnippet 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `snippet` | Snippet | 突变后的代码段 |
## DastSiteProfileCreatePayload[](#dastsiteprofilecreatepayload "Permalink")
自动生成的 DastSiteProfileCreate 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `id` | ID | 网站配置文件的 ID. |
## DeleteAnnotationPayload[](#deleteannotationpayload "Permalink")
自动生成的 DeleteAnnotation 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## DeleteJobsResponse[](#deletejobsresponse "Permalink")
来自 AdminSidekiqQueuesDeleteJobs 突变的响应.
| Name | Type | Description |
| --- | --- | --- |
| `completed` | Boolean | 是否及时处理了整个队列; 如果没有,重试相同的请求是安全的 |
| `deletedJobs` | Int | 删除的匹配作业数 |
| `queueSize` | Int | 处理后的队列大小 |
## Design[](#design "Permalink")
单一设计
| Name | Type | Description |
| --- | --- | --- |
| `diffRefs` | DiffRefs! | 此设计的差异参考 |
| `event` | DesignVersionEvent! | 当前版本中该设计的更改方式 |
| `filename` | String! | 设计的文件名 |
| `fullPath` | String! | 设计文件的完整路径 |
| `id` | ID! | 此设计的 ID |
| `image` | String! | 完整尺寸图片的网址 |
| `imageV432x230` | String | 调整了设计网址的大小,以适合 432x230 的范围. 如果尚未生成图像,则为`null` |
| `issue` | Issue! | 设计属于的问题 |
| `notesCount` | Int! | 用户为此设计创建的注释总数 |
| `project` | Project! | 设计所属的项目 |
## DesignAtVersion[](#designatversion "Permalink")
固定到特定版本的设计. 图像字段反映了相关版本的设计.
| Name | Type | Description |
| --- | --- | --- |
| `design` | Design! | 基础设计. |
| `diffRefs` | DiffRefs! | 此设计的差异参考 |
| `event` | DesignVersionEvent! | 当前版本中该设计的更改方式 |
| `filename` | String! | 设计的文件名 |
| `fullPath` | String! | 设计文件的完整路径 |
| `id` | ID! | 此设计的 ID |
| `image` | String! | 完整尺寸图片的网址 |
| `imageV432x230` | String | 调整了设计网址的大小,以适合 432x230 的范围. 如果尚未生成图像,则为`null` |
| `issue` | Issue! | 设计属于的问题 |
| `notesCount` | Int! | 用户为此设计创建的注释总数 |
| `project` | Project! | 设计所属的项目 |
| `version` | DesignVersion! | 此版本设计版本固定到的版本 |
## DesignCollection[](#designcollection "Permalink")
设计的集合.
| Name | Type | Description |
| --- | --- | --- |
| `design` | Design | 查找特定的设计 |
| `designAtVersion` | DesignAtVersion | 查找版本设计 |
| `issue` | Issue! | 与设计收藏相关的问题 |
| `project` | Project! | 与设计收藏关联的项目 |
| `version` | DesignVersion | 特定版本 |
## DesignManagement[](#designmanagement "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `designAtVersion` | DesignAtVersion | 查找版本设计 |
| `version` | DesignVersion | 查找版本 |
## DesignManagementDeletePayload[](#designmanagementdeletepayload "Permalink")
自动生成的 DesignManagementDelete 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `version` | DesignVersion | 删除了设计的新版本 |
## DesignManagementUploadPayload[](#designmanagementuploadpayload "Permalink")
自动生成的 DesignManagementUpload 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `designs` | 设计! =>数组 | 突变上传的设计 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `skippedDesigns` | 设计! =>数组 | 由于上一版本以来其内容没有更改,因此从上载中跳过的任何设计 |
## DesignVersion[](#designversion "Permalink")
在其中添加,修改或删除设计的特定版本
| Name | Type | Description |
| --- | --- | --- |
| `designAtVersion` | DesignAtVersion! | 此版本的特定设计,只要该版本可见 |
| `id` | ID! | 设计版本号 |
| `sha` | ID! | 设计版本的 SHA |
## DestroyNotePayload[](#destroynotepayload "Permalink")
自动生成的销毁返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `note` | Note | 突变后的音符 |
## DestroySnippetPayload[](#destroysnippetpayload "Permalink")
自动生成的 DestroySnippet 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `snippet` | Snippet | 突变后的代码段 |
## DetailedStatus[](#detailedstatus "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `detailsPath` | String! | 管道状态的详细信息路径 |
| `favicon` | String! | 管道状态图标 |
| `group` | String! | 组管道状态 |
| `hasDetails` | Boolean! | 指示管道状态是否有更多详细信息 |
| `icon` | String! | 管道状态图标 |
| `label` | String! | 管道状态标签 |
| `text` | String! | 管道状态文字 |
| `tooltip` | String! | 与管道状态相关的工具提示 |
## DiffPosition[](#diffposition "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `diffRefs` | DiffRefs! | 评论时有关分支,HEAD 和基础的信息 |
| `filePath` | String! | 更改文件的路径 |
| `height` | Int | 图片总高度 |
| `newLine` | Int | HEAD SHA 上的线已更改 |
| `newPath` | String | HEAD SHA 上文件的路径 |
| `oldLine` | Int | 起始 SHA 上已更改的行 |
| `oldPath` | String | 起始 SHA 上文件的路径 |
| `positionType` | DiffPositionType! | 位置所指的文件类型 |
| `width` | Int | 图片总宽度 |
| `x` | Int | 笔记的 X 位置 |
| `y` | Int | 音符的 Y 位置 |
## DiffRefs[](#diffrefs "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `baseSha` | String | Merge base of the branch the comment was made on |
| `headSha` | String! | 发表评论时,HEAD 的 SHA |
| `startSha` | String! | 与之比较的分支的 SHA |
## DiffStats[](#diffstats "Permalink")
更改为单个文件
| Name | Type | Description |
| --- | --- | --- |
| `additions` | Int! | 添加到此文件的行数 |
| `deletions` | Int! | 从此文件中删除的行数 |
| `path` | String! | 相对于存储库根的文件路径 |
## DiffStatsSummary[](#diffstatssummary "Permalink")
汇总汇总
| Name | Type | Description |
| --- | --- | --- |
| `additions` | Int! | 添加的行数 |
| `changes` | Int! | 行数已更改 |
| `deletions` | Int! | 删除的行数 |
| `fileCount` | Int! | 文件数量已更改 |
## Discussion[](#discussion "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time! | 讨论创建的时间戳 |
| `id` | ID! | 讨论的 ID |
| `replyId` | ID! | 用来回复此讨论的 ID |
| `resolvable` | Boolean! | 指示对象是否可以解析 |
| `resolved` | Boolean! | 指示对象是否已解析 |
| `resolvedAt` | Time | 解析对象的时间戳 |
| `resolvedBy` | User | 解决对象的用户 |
## DiscussionToggleResolvePayload[](#discussiontoggleresolvepayload "Permalink")
自动生成的 DiscussionToggleResolve 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `discussion` | Discussion | 突变后的讨论 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## DismissVulnerabilityPayload[](#dismissvulnerabilitypayload "Permalink")
自动生成的 DismissVulnerability 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `vulnerability` | Vulnerability | 解雇后的漏洞 |
## Environment[](#environment "Permalink")
描述项目的代码部署位置
| Name | Type | Description |
| --- | --- | --- |
| `id` | ID! | 环境 ID |
| `metricsDashboard` | MetricsDashboard | 环境的指标仪表板架构 |
| `name` | String! | 易读的环境名称 |
| `state` | String! | 环境状态,例如:可用/已停止 |
## Epic[](#epic "Permalink")
代表史诗.
| Name | Type | Description |
| --- | --- | --- |
| `author` | User! | 史诗的作者 |
| `closedAt` | Time | 史诗关闭的时间戳 |
| `confidential` | Boolean | 指示该史诗是否为机密 |
| `createdAt` | Time | 史诗创作的时间戳 |
| `descendantCounts` | EpicDescendantCount | 打开和关闭的后代史诗和问题的数量 |
| `descendantWeightSum` | EpicDescendantWeights | 史诗及其后代中未解决和未解决问题的总权重 |
| `description` | String | 史诗的描述 |
| `downvotes` | Int! | 史诗获得的降票数 |
| `dueDate` | Time | 史诗的截止日期 |
| `dueDateFixed` | Time | 史诗的固定截止日期 |
| `dueDateFromMilestones` | Time | 从里程碑继承了史诗的到期日 |
| `dueDateIsFixed` | Boolean | 指示是否已手动设置截止日期 |
| `group` | Group! | 史诗所属的组 |
| `hasChildren` | Boolean! | 指示史诗是否有孩子 |
| `hasIssues` | Boolean! | 指示史诗是否有直接问题 |
| `hasParent` | Boolean! | 指示该史诗是否具有父史诗 |
| `healthStatus` | EpicHealthStatus | Current health status of the epic |
| `id` | ID! | 史诗编号 |
| `iid` | ID! | 史诗的内部 ID |
| `parent` | Epic | 史诗的父史诗 |
| `reference` | String! | 史诗的内部参考. 默认以缩写形式返回 |
| `relationPath` | String | 史诗问题的 URI 路径 |
| `relativePosition` | Int | 史诗在史诗树中的相对位置 |
| `startDate` | Time | 史诗的开始日期 |
| `startDateFixed` | Time | 固定的史诗开始日期 |
| `startDateFromMilestones` | Time | 从里程碑继承了史诗的开始日期 |
| `startDateIsFixed` | Boolean | 指示开始日期是否已手动设置 |
| `state` | EpicState! | 史诗般的状态 |
| `subscribed` | Boolean! | 指示当前登录的用户已订阅史诗 |
| `title` | String | 史诗的标题 |
| `updatedAt` | Time | 史诗最后一次活动的时间戳 |
| `upvotes` | Int! | 史诗已收到的投票数 |
| `userPermissions` | EpicPermissions! | 当前用户对该资源的权限 |
| `webPath` | String! | 史诗的网络路径 |
| `webUrl` | String! | 史诗的网址 |
## EpicAddIssuePayload[](#epicaddissuepayload "Permalink")
自动生成的 EpicAddIssue 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `epic` | Epic | 突变后的史诗 |
| `epicIssue` | EpicIssue | 史诗般的关系 |
| `errors` | 串! =>数组 | Errors encountered during execution of the mutation. |
## EpicDescendantCount[](#epicdescendantcount "Permalink")
后代史诗的计数.
| Name | Type | Description |
| --- | --- | --- |
| `closedEpics` | Int | 封闭亚史诗数量 |
| `closedIssues` | Int | 已解决的史诗问题的数量 |
| `openedEpics` | Int | 打开的子史诗数量 |
| `openedIssues` | Int | 公开史诗问题的数量 |
## EpicDescendantWeights[](#epicdescendantweights "Permalink")
开放和封闭后代问题的总权重
| Name | Type | Description |
| --- | --- | --- |
| `closedIssues` | Int | 此史诗(包括史诗后代)中已完成(已关闭)期刊的总权重 |
| `openedIssues` | Int | 此史诗(包括史诗后代)中未解决问题的总权重 |
## EpicHealthStatus[](#epichealthstatus "Permalink")
儿童健康状况
| Name | Type | Description |
| --- | --- | --- |
| `issuesAtRisk` | Int | 有风险的问题数量 |
| `issuesNeedingAttention` | Int | 需要注意的问题数量 |
| `issuesOnTrack` | Int | 进行中的问题数量 |
## EpicIssue[](#epicissue "Permalink")
史诗与问题之间的关系
| Name | Type | Description |
| --- | --- | --- |
| `author` | User! | 造成问题的使用者 |
| `closedAt` | Time | 该问题何时结束的时间戳 |
| `confidential` | Boolean! | 表示问题是机密的 |
| `createdAt` | Time! | 问题创建时间的时间戳记 |
| `description` | String | 问题说明 |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `designCollection` | DesignCollection | 与此问题相关的设计图像的收集 |
| `designs` | DesignCollection | **不推荐使用:**使用`designCollection` . 在 12.2 中弃用 |
| `discussionLocked` | Boolean! | 表示讨论已锁定在该问题上 |
| `downvotes` | Int! | 问题已收到的否决票数 |
| `dueDate` | Time | 发行日期 |
| `epic` | Epic | 此问题所属的史诗 |
| `epicIssueId` | ID! | 史诗般的关系的 ID |
| `healthStatus` | HealthStatus | 当前的健康状况. 如果禁用了`save_issuable_health_status`功能标志,则返回 null. |
| `id` | ID | 史诗关系的全局 ID |
| `iid` | ID! | 问题的内部 ID |
| `iteration` | Iteration | 迭代问题 |
| `milestone` | Milestone | 问题的里程碑 |
| `reference` | String! | 内部参考的问题. 默认以缩写形式返回 |
| `relationPath` | String | 史诗问题的 URI 路径 |
| `relativePosition` | Int | 问题的相对位置(用于在史诗树和问题板上定位) |
| `state` | IssueState! | 问题状态 |
| `subscribed` | Boolean! | 指示当前登录的用户已订阅该问题 |
| `taskCompletionStatus` | TaskCompletionStatus! | 问题的任务完成状态 |
| `timeEstimate` | Int! | 问题的时间估算 |
| `title` | String! | 问题标题 |
| `titleHtml` | String | GitLab 风味 Markdown `title`渲染 |
| `totalTimeSpent` | Int! | 报告在此问题上花费的总时间 |
| `updatedAt` | Time! | 问题上次更新的时间戳 |
| `upvotes` | Int! | 问题已收到的投票数 |
| `userNotesCount` | Int! | 用户对此问题的注释数 |
| `userPermissions` | IssuePermissions! | 当前用户对该资源的权限 |
| `webPath` | String! | 问题的网络路径 |
| `webUrl` | String! | 问题的网址 |
| `weight` | Int | 问题的权重 |
## EpicPermissions[](#epicpermissions "Permalink")
检查史诗级当前用户的权限
| Name | Type | Description |
| --- | --- | --- |
| `adminEpic` | Boolean! | 指示用户可以对此资源执行`admin_epic` |
| `awardEmoji` | Boolean! | 表示用户可以在此资源上执行`award_emoji` |
| `createEpic` | Boolean! | 指示用户可以在此资源上执行`create_epic` |
| `createNote` | Boolean! | 指示用户可以在此资源上执行`create_note` |
| `destroyEpic` | Boolean! | 指示用户可以对此资源执行`destroy_epic` |
| `readEpic` | Boolean! | 指示用户可以对此资源执行`read_epic` |
| `readEpicIid` | Boolean! | 指示用户可以对此资源执行`read_epic_iid` |
| `updateEpic` | Boolean! | 指示用户可以对此资源执行`update_epic` |
## EpicSetSubscriptionPayload[](#epicsetsubscriptionpayload "Permalink")
自动生成的 EpicSetSubscription 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `epic` | Epic | 突变后的史诗 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## EpicTreeReorderPayload[](#epictreereorderpayload "Permalink")
自动生成的 EpicTreeReorder 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## GeoNode[](#geonode "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `containerRepositoriesMaxCapacity` | Int | 此辅助节点的容器存储库同步的最大并发性 |
| `enabled` | Boolean | 指示是否启用了此地理节点 |
| `filesMaxCapacity` | Int | 此辅助节点的 LFS /附件回填的最大并发性 |
| `id` | ID! | 此 GeoNode 的 ID |
| `internalUrl` | String | 在主节点上定义的 URL,辅助节点应使用该 URL 与之联系 |
| `minimumReverificationInterval` | Int | 存储库验证有效的时间间隔(以天为单位). 一旦过期,它将被重新验证 |
| `name` | String | 此地理节点的唯一标识符 |
| `primary` | Boolean | 指示此地理节点是否为主要节点 |
| `reposMaxCapacity` | Int | 此辅助节点的存储库回填的最大并发性 |
| `selectiveSyncShards` | 串! =>数组 | 如果`selective_sync_type` == `shards` ,应同步其项目的存储库存储 |
| `selectiveSyncType` | String | 指示同步是否仅限于特定的组或分片 |
| `syncObjectStorage` | Boolean | 指示此辅助节点是否将复制对象存储中的 Blob |
| `url` | String | 此地理位置节点的面向用户的网址 |
| `verificationMaxCapacity` | Int | 此辅助节点的存储库验证的最大并发性 |
## GrafanaIntegration[](#grafanaintegration "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time! | 问题创建的时间戳 |
| `enabled` | Boolean! | 指示是否启用 Grafana 集成 |
| `grafanaUrl` | String! | 用于 Grafana 集成的 Grafana 主机的 URL |
| `id` | ID! | Grafana 集成的内部 ID |
| `token` | String! | **不推荐使用:**出于安全原因,纯文本令牌已被屏蔽. 在 12.7 中弃用 |
| `updatedAt` | Time! | 问题上次活动的时间戳 |
## Group[](#group "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `autoDevopsEnabled` | Boolean | 指示是否为该组内的所有项目启用了 Auto DevOps |
| `avatarUrl` | String | 群组的头像网址 |
| `board` | Board | 小组的一个董事会 |
| `description` | String | 命名空间的描述 |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `emailsDisabled` | Boolean | 指示组是否禁用了电子邮件通知 |
| `epic` | Epic | 查找单个史诗 |
| `epicsEnabled` | Boolean | 指示是否为名称空间启用了 Epics |
| `fullName` | String! | 命名空间的全名 |
| `fullPath` | ID! | 命名空间的完整路径 |
| `groupTimelogsEnabled` | Boolean | 指示是否为名称空间启用了组时间日志 |
| `id` | ID! | 命名空间的 ID |
| `label` | Label | 该组可用的标签 |
| `lfsEnabled` | Boolean | 指示是否为名称空间启用了大文件存储(LFS) |
| `mentionsDisabled` | Boolean | 指示是否禁止某人被提及 |
| `name` | String! | 命名空间的名称 |
| `parent` | Group | 家长组 |
| `path` | String! | 命名空间的路径 |
| `projectCreationLevel` | String | 在组中创建项目所需的权限级别 |
| `requestAccessEnabled` | Boolean | 指示用户是否可以请求访问名称空间 |
| `requireTwoFactorAuthentication` | Boolean | 指示是否需要该组中的所有用户来设置两因素身份验证 |
| `rootStorageStatistics` | RootStorageStatistics | 命名空间的聚合存储统计信息. 仅适用于根名称空间 |
| `shareWithGroupLock` | Boolean | 指示是否禁止与该组中的另一个组共享项目 |
| `storageSizeLimit` | Float | 根名称空间的总存储限制(以字节为单位) |
| `subgroupCreationLevel` | String | 在组内创建子组所需的权限级别 |
| `temporaryStorageIncreaseEndsOn` | Time | 直到临时存储增加生效的日期 |
| `twoFactorGracePeriod` | Int | 强制执行两因素身份验证的时间 |
| `userPermissions` | GroupPermissions! | 当前用户对该资源的权限 |
| `visibility` | String | 名称空间的可见性 |
| `webUrl` | String! | 网上论坛网址 |
## GroupMember[](#groupmember "Permalink")
代表小组成员
| Name | Type | Description |
| --- | --- | --- |
| `accessLevel` | AccessLevel | GitLab ::访问级别 |
| `createdAt` | Time | 创建成员的日期和时间 |
| `createdBy` | User | 授权会员的用户 |
| `expiresAt` | Time | 成员资格到期的日期和时间 |
| `group` | Group | 用户所属的组 |
| `updatedAt` | Time | 成员的最新更新日期和时间 |
| `userPermissions` | GroupPermissions! | 当前用户对该资源的权限 |
## GroupPermissions[](#grouppermissions "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `readGroup` | Boolean! | 指示用户可以对此资源执行`read_group` |
## Issue[](#issue "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `author` | User! | 造成问题的使用者 |
| `closedAt` | Time | 该问题何时结束的时间戳 |
| `confidential` | Boolean! | 表示问题是机密的 |
| `createdAt` | Time! | 问题创建时间的时间戳记 |
| `description` | String | 问题说明 |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `designCollection` | DesignCollection | 与此问题相关的设计图像的收集 |
| `designs` | DesignCollection | **不推荐使用:**使用`designCollection` . 在 12.2 中弃用 |
| `discussionLocked` | Boolean! | 表示讨论已锁定在该问题上 |
| `downvotes` | Int! | 问题已收到的否决票数 |
| `dueDate` | Time | 发行日期 |
| `epic` | Epic | 此问题所属的史诗 |
| `healthStatus` | HealthStatus | 当前的健康状况. 如果禁用了`save_issuable_health_status`功能标志,则返回 null. |
| `id` | ID! | 问题编号 |
| `iid` | ID! | 问题的内部 ID |
| `iteration` | Iteration | 迭代问题 |
| `milestone` | Milestone | 问题的里程碑 |
| `reference` | String! | 内部参考的问题. 默认以缩写形式返回 |
| `relativePosition` | Int | 问题的相对位置(用于在史诗树和问题板上定位) |
| `state` | IssueState! | 问题状态 |
| `subscribed` | Boolean! | 指示当前登录的用户已订阅该问题 |
| `taskCompletionStatus` | TaskCompletionStatus! | 问题的任务完成状态 |
| `timeEstimate` | Int! | 问题的时间估算 |
| `title` | String! | 问题标题 |
| `titleHtml` | String | GitLab 风味 Markdown `title`渲染 |
| `totalTimeSpent` | Int! | 报告在此问题上花费的总时间 |
| `updatedAt` | Time! | 问题上次更新的时间戳 |
| `upvotes` | Int! | 问题已收到的投票数 |
| `userNotesCount` | Int! | 用户对此问题的注释数 |
| `userPermissions` | IssuePermissions! | 当前用户对该资源的权限 |
| `webPath` | String! | 问题的网络路径 |
| `webUrl` | String! | 问题的网址 |
| `weight` | Int | 问题的权重 |
## IssuePermissions[](#issuepermissions "Permalink")
检查当前用户在问题上的权限
| Name | Type | Description |
| --- | --- | --- |
| `adminIssue` | Boolean! | 指示用户可以对此资源执行`admin_issue` |
| `createDesign` | Boolean! | 指示用户可以对此资源执行`create_design` |
| `createNote` | Boolean! | 指示用户可以在此资源上执行`create_note` |
| `destroyDesign` | Boolean! | 指示用户可以对此资源执行`destroy_design` |
| `readDesign` | Boolean! | 指示用户可以对此资源执行`read_design` |
| `readIssue` | Boolean! | 指示用户可以对此资源执行`read_issue` |
| `reopenIssue` | Boolean! | 指示用户可以对此资源执行`reopen_issue` |
| `updateIssue` | Boolean! | 指示用户可以对此资源执行`update_issue` |
## IssueSetConfidentialPayload[](#issuesetconfidentialpayload "Permalink")
自动生成的 IssueSetConfidential 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后的问题 |
## IssueSetDueDatePayload[](#issuesetduedatepayload "Permalink")
自动生成的 IssueSetDueDate 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后的问题 |
## IssueSetIterationPayload[](#issuesetiterationpayload "Permalink")
自动生成的 IssueSetIteration 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后的问题 |
## IssueSetLockedPayload[](#issuesetlockedpayload "Permalink")
自动生成的 IssueSetLocked 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后的问题 |
## IssueSetWeightPayload[](#issuesetweightpayload "Permalink")
自动生成的 IssueSetWeight 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后的问题 |
## Iteration[](#iteration "Permalink")
表示一个迭代对象.
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time! | 迭代创建的时间戳 |
| `description` | String | 迭代描述 |
| `dueDate` | Time | 迭代到期日期的时间戳 |
| `id` | ID! | 迭代 ID |
| `iid` | ID! | 迭代的内部 ID |
| `startDate` | Time | 迭代开始日期的时间戳 |
| `state` | IterationState! | 迭代状态 |
| `title` | String! | 迭代标题 |
| `updatedAt` | Time! | 上次迭代更新的时间戳 |
| `webPath` | String! | 迭代的 Web 路径 |
| `webUrl` | String! | 迭代的 Web URL |
## JiraImport[](#jiraimport "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time | 创建 Jira 导入的时间戳 |
| `failedToImportCount` | Int! | 导入失败的问题数 |
| `importedIssuesCount` | Int! | 成功导入的问题数 |
| `jiraProjectKey` | String! | 导入的 Jira 项目的项目密钥 |
| `scheduledAt` | Time | 计划导入 Jira 的时间戳 |
| `scheduledBy` | User | 开始导入 Jira 的用户 |
| `totalIssueCount` | Int! | 尝试导入的问题总数 |
## JiraImportStartPayload[](#jiraimportstartpayload "Permalink")
自动生成的 JiraImportStart 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | Errors encountered during execution of the mutation. |
| `jiraImport` | JiraImport | 突变后的 Jira 导入数据 |
## JiraImportUsersPayload[](#jiraimportuserspayload "Permalink")
自动生成的 JiraImportUsers 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `jiraUsers` | JiraUser! =>数组 | 从 Jira 返回的用户,并通过电子邮件和姓名进行匹配(如果可能). |
## JiraProject[](#jiraproject "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `key` | String! | 吉拉项目的关键 |
| `name` | String | Jira 项目的名称 |
| `projectId` | Int! | Jira 项目的 ID |
## JiraService[](#jiraservice "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `active` | Boolean | 指示服务是否处于活动状态 |
| `projects` | JiraProjectConnection | 通过 Jira REST API 获取的所有 Jira 项目的列表 |
| `type` | String | 服务的类别名称 |
## JiraUser[](#jirauser "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `gitlabId` | Int | 匹配的 GitLab 用户的 ID |
| `gitlabName` | String | 匹配的 GitLab 用户名 |
| `gitlabUsername` | String | 匹配的 GitLab 用户的用户名 |
| `jiraAccountId` | String! | Jira 用户的帐户 ID |
| `jiraDisplayName` | String! | Jira 用户的显示名称 |
| `jiraEmail` | String | Jira 用户的电子邮件,仅针对具有公共电子邮件的用户返回 |
## Label[](#label "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `color` | String! | 标签的背景色 |
| `description` | String | 标签的说明(Markdown 呈现为 HTML 以进行缓存) |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `id` | ID! | 标签编号 |
| `textColor` | String! | 标签的文字颜色 |
| `title` | String! | 标签内容 |
## MarkAsSpamSnippetPayload[](#markasspamsnippetpayload "Permalink")
自动生成的 MarkAsSpamSnippet 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `snippet` | Snippet | 突变后的代码段 |
## MergeRequest[](#mergerequest "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `allowCollaboration` | Boolean | 指示目标项目的成员是否可以推送到分叉 |
| `author` | User | 创建此合并请求的用户 |
| `createdAt` | Time! | 创建合并请求的时间戳 |
| `defaultMergeCommitMessage` | String | 合并请求的默认合并提交消息 |
| `description` | String | 合并请求的描述(Markdown 渲染为 HTML 以进行缓存) |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `diffHeadSha` | String | 合并请求的不同头 SHA |
| `diffRefs` | DiffRefs | 此合并请求的基础 SHA,头部 SHA 和起始 SHA 的引用 |
| `diffStats` | DiffStats! =>数组 | 有关在此合并请求中更改了哪些文件的详细信息 |
| `diffStatsSummary` | DiffStatsSummary | 在此合并请求中更改了哪些文件的摘要 |
| `discussionLocked` | Boolean! | 指示是否仅将对合并请求的注释锁定为成员 |
| `downvotes` | Int! | 合并请求的否决票数 |
| `forceRemoveSourceBranch` | Boolean | 指示合并后项目设置是否会导致源分支删除 |
| `headPipeline` | Pipeline | 在合并请求的分支 HEAD 上运行的管道 |
| `id` | ID! | 合并请求的 ID |
| `iid` | String! | 合并请求的内部 ID |
| `inProgressMergeCommitSha` | String | 如果合并正在进行,则提交合并请求的 SHA |
| `mergeCommitMessage` | String | **不推荐使用:**使用`defaultMergeCommitMessage` . 在 11.8 中已弃用 |
| `mergeCommitSha` | String | 合并请求提交的 SHA(一旦合并就设置) |
| `mergeError` | String | 由于合并错误而导致的错误消息 |
| `mergeOngoing` | Boolean! | 指示当前是否正在发生合并 |
| `mergeStatus` | String | 合并请求的状态 |
| `mergeWhenPipelineSucceeds` | Boolean | 指示在管道成功(MWPS)时是否已将合并设置为要合并 |
| `mergeableDiscussionsState` | Boolean | 指示合并请求中的所有讨论是否都已解决,从而允许合并请求被合并 |
| `mergedAt` | Time | 合并请求合并的时间戳记;如果未合并,则为 null |
| `milestone` | Milestone | 合并请求的里程碑 |
| `project` | Project! | target_project 的别名 |
| `projectId` | Int! | 合并请求项目的 ID |
| `rebaseCommitSha` | String | 重新设置合并请求的提交 SHA |
| `rebaseInProgress` | Boolean! | 指示合并请求当前是否正在进行重新设置 |
| `reference` | String! | 合并请求的内部参考. 默认以缩写形式返回 |
| `shouldBeRebased` | Boolean! | 指示合并请求是否将被重定基础 |
| `shouldRemoveSourceBranch` | Boolean | 指示在合并后是否会删除合并请求的源分支 |
| `sourceBranch` | String! | 合并请求的源分支 |
| `sourceBranchExists` | Boolean! | 指示合并请求的源分支是否存在 |
| `sourceProject` | Project | 合并请求的源项目 |
| `sourceProjectId` | Int | 合并请求源项目的 ID |
| `state` | MergeRequestState! | 合并请求的状态 |
| `subscribed` | Boolean! | 指示当前登录的用户是否订阅了此合并请求 |
| `targetBranch` | String! | 合并请求的目标分支 |
| `targetBranchExists` | Boolean! | 指示合并请求的目标分支是否存在 |
| `targetProject` | Project! | 合并请求的目标项目 |
| `targetProjectId` | Int! | 合并请求目标项目的 ID |
| `taskCompletionStatus` | TaskCompletionStatus! | 任务的完成状态 |
| `timeEstimate` | Int! | 合并请求的时间估算 |
| `title` | String! | 合并请求的标题 |
| `titleHtml` | String | GitLab 风味 Markdown `title`渲染 |
| `totalTimeSpent` | Int! | 报告为在合并请求上花费的总时间 |
| `updatedAt` | Time! | 合并请求上次更新的时间戳 |
| `upvotes` | Int! | 合并请求的投票数 |
| `userNotesCount` | Int | 用户记录合并请求的数量 |
| `userPermissions` | MergeRequestPermissions! | 当前用户对该资源的权限 |
| `webUrl` | String | 合并请求的网址 |
| `workInProgress` | Boolean! | 指示合并请求是否正在进行中(WIP) |
## MergeRequestCreatePayload[](#mergerequestcreatepayload "Permalink")
自动生成的 MergeRequestCreate 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestPermissions[](#mergerequestpermissions "Permalink")
检查合并请求中当前用户的权限
| Name | Type | Description |
| --- | --- | --- |
| `adminMergeRequest` | Boolean! | 指示用户可以对此资源执行`admin_merge_request` |
| `cherryPickOnCurrentMergeRequest` | Boolean! | 表示用户可以对此资源执行`cherry_pick_on_current_merge_request` |
| `createNote` | Boolean! | 指示用户可以在此资源上执行`create_note` |
| `pushToSourceBranch` | Boolean! | 指示用户可以对此资源执行`push_to_source_branch` |
| `readMergeRequest` | Boolean! | 指示用户可以对此资源执行`read_merge_request` |
| `removeSourceBranch` | Boolean! | 指示用户可以对此资源执行`remove_source_branch` |
| `revertOnCurrentMergeRequest` | Boolean! | 指示用户可以对此资源执行`revert_on_current_merge_request` |
| `updateMergeRequest` | Boolean! | 指示用户可以对此资源执行`update_merge_request` |
## MergeRequestSetAssigneesPayload[](#mergerequestsetassigneespayload "Permalink")
自动生成的 MergeRequestSetAssignees 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestSetLabelsPayload[](#mergerequestsetlabelspayload "Permalink")
自动生成的 MergeRequestSetLabels 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestSetLockedPayload[](#mergerequestsetlockedpayload "Permalink")
自动生成的 MergeRequestSetLocked 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestSetMilestonePayload[](#mergerequestsetmilestonepayload "Permalink")
自动生成的 MergeRequestSetMilestone 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestSetSubscriptionPayload[](#mergerequestsetsubscriptionpayload "Permalink")
自动生成的 MergeRequestSetSubscription 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestSetWipPayload[](#mergerequestsetwippayload "Permalink")
自动生成的 MergeRequestSetWip 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## MergeRequestUpdatePayload[](#mergerequestupdatepayload "Permalink")
自动生成的 MergeRequestUpdate 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `mergeRequest` | MergeRequest | 突变后的合并请求 |
## Metadata[](#metadata "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `revision` | String! | Revision |
| `version` | String! | Version |
## MetricsDashboard[](#metricsdashboard "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `path` | String | 具有仪表板定义的文件的路径 |
| `schemaValidationWarnings` | 串! =>数组 | 仪表板架构验证警告 |
## MetricsDashboardAnnotation[](#metricsdashboardannotation "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `description` | String | 注释说明 |
| `endingAt` | Time | 注释时间跨度的时间戳标记结束 |
| `id` | ID! | 注释的 ID |
| `panelId` | String | 注释应作用于的仪表板面板的 ID |
| `startingAt` | Time | 带注释的时间跨度的时间戳标记开始 |
## Milestone[](#milestone "Permalink")
代表一个里程碑.
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time! | 里程碑创建的时间戳 |
| `description` | String | 里程碑说明 |
| `dueDate` | Time | 里程碑到期日期的时间戳记 |
| `groupMilestone` | Boolean! | 指示里程碑是否在组级别 |
| `id` | ID! | 里程碑的 ID |
| `projectMilestone` | Boolean! | 指示里程碑是否在项目级别 |
| `startDate` | Time | 里程碑开始日期的时间戳记 |
| `state` | MilestoneStateEnum! | 里程碑状态 |
| `stats` | MilestoneStats | 里程碑统计 |
| `subgroupMilestone` | Boolean! | 指示里程碑是否在子组级别 |
| `title` | String! | 里程碑标题 |
| `updatedAt` | Time! | 最近里程碑更新的时间戳 |
| `webPath` | String! | 里程碑的 Web 路径 |
## MilestoneStats[](#milestonestats "Permalink")
包含有关里程碑的统计信息
| Name | Type | Description |
| --- | --- | --- |
| `closedIssuesCount` | Int | 与里程碑相关的已解决问题的数量 |
| `totalIssuesCount` | Int | 与里程碑相关的总问题数 |
## Namespace[](#namespace "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `description` | String | 命名空间的描述 |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `fullName` | String! | 命名空间的全名 |
| `fullPath` | ID! | 命名空间的完整路径 |
| `id` | ID! | 命名空间的 ID |
| `lfsEnabled` | Boolean | 指示是否为名称空间启用了大文件存储(LFS) |
| `name` | String! | 命名空间的名称 |
| `path` | String! | 命名空间的路径 |
| `requestAccessEnabled` | Boolean | 指示用户是否可以请求访问名称空间 |
| `rootStorageStatistics` | RootStorageStatistics | 命名空间的聚合存储统计信息. 仅适用于根名称空间 |
| `storageSizeLimit` | Float | 根名称空间的总存储限制(以字节为单位) |
| `temporaryStorageIncreaseEndsOn` | Time | 直到临时存储增加生效的日期 |
| `visibility` | String | 名称空间的可见性 |
## Note[](#note "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `author` | User! | 撰写此笔记的用户 |
| `body` | String! | 注释内容 |
| `bodyHtml` | String | GitLab 风味 Markdown 渲染`note` |
| `confidential` | Boolean | 指示此注释是否保密 |
| `createdAt` | Time! | 笔记创建的时间戳 |
| `discussion` | Discussion | 本说明的讨论属于 |
| `id` | ID! | 笔记编号 |
| `position` | DiffPosition | 此注释在差异上的位置 |
| `project` | Project | 与笔记相关的项目 |
| `resolvable` | Boolean! | 指示对象是否可以解析 |
| `resolved` | Boolean! | 指示对象是否已解析 |
| `resolvedAt` | Time | 解析对象的时间戳 |
| `resolvedBy` | User | 解决对象的用户 |
| `system` | Boolean! | 指示此注释是由系统还是由用户创建的 |
| `systemNoteIconName` | String | 系统注释对应的图标名称 |
| `updatedAt` | Time! | 笔记上一次活动的时间戳 |
| `userPermissions` | NotePermissions! | 当前用户对该资源的权限 |
## NotePermissions[](#notepermissions "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `adminNote` | Boolean! | 指示用户可以对此资源执行`admin_note` |
| `awardEmoji` | Boolean! | 表示用户可以在此资源上执行`award_emoji` |
| `createNote` | Boolean! | 指示用户可以在此资源上执行`create_note` |
| `readNote` | Boolean! | 指示用户可以对此资源执行`read_note` |
| `resolveNote` | Boolean! | 指示用户可以对此资源执行`resolve_note` |
## Package[](#package "Permalink")
代表包裹
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time! | 创建日期 |
| `id` | ID! | 包裹 ID |
| `name` | String! | 包装名称 |
| `packageType` | PackageTypeEnum! | 包装类型 |
| `updatedAt` | Time! | 更新日期 |
| `version` | String | 包的版本 |
## PackageFileRegistry[](#packagefileregistry "Permalink")
表示软件包文件的同步和验证状态
| Name | Type | Description |
| --- | --- | --- |
| `createdAt` | Time | PackageFileRegistry 创建时的时间戳记 |
| `id` | ID! | PackageFileRegistry 的 ID |
| `lastSyncFailure` | String | PackageFileRegistry 同步期间的错误消息 |
| `lastSyncedAt` | Time | PackageFileRegistry 最近一次成功同步的时间戳 |
| `packageFileId` | ID! | PackageFile 的 ID |
| `retryAt` | Time | 时间戳,之后 PackageFileRegistry 应该重新同步 |
| `retryCount` | Int | PackageFileRegistry 连续失败的同步尝试次数 |
| `state` | RegistryState | PackageFileRegistry 的同步状态 |
## PageInfo[](#pageinfo "Permalink")
有关连接中的分页的信息.
| Name | Type | Description |
| --- | --- | --- |
| `endCursor` | String | 向前分页时,光标继续. |
| `hasNextPage` | Boolean! | 在向前分页时,还有更多项目吗? |
| `hasPreviousPage` | Boolean! | 向后分页时,还有更多项目吗? |
| `startCursor` | String | 向后分页时,光标继续. |
## Pipeline[](#pipeline "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `beforeSha` | String | 源分支的基本 SHA |
| `committedAt` | Time | 管道提交的时间戳 |
| `coverage` | Float | 覆盖率 |
| `createdAt` | Time! | 管道创建的时间戳 |
| `detailedStatus` | DetailedStatus! | 管道的详细状态 |
| `duration` | Int | 管道持续时间(以秒为单位) |
| `finishedAt` | Time | 管道完成的时间戳 |
| `id` | ID! | 管道 ID |
| `iid` | String! | 管道的内部 ID |
| `securityReportSummary` | SecurityReportSummary | 管道的每个安全扫描程序的漏洞和扫描的资源计数 |
| `sha` | String! | 管道提交的 SHA |
| `startedAt` | Time | 管道启动的时间戳 |
| `status` | PipelineStatusEnum! | 管道的状态(已创建,正在等待 _ 资源,正在准备,正在挂起,正在运行,失败,成功,已取消,已跳过,已手动,已计划) |
| `updatedAt` | Time! | 管道上次活动的时间戳 |
| `userPermissions` | PipelinePermissions! | 当前用户对该资源的权限 |
## PipelinePermissions[](#pipelinepermissions "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `adminPipeline` | Boolean! | 指示用户可以对此资源执行`admin_pipeline` |
| `destroyPipeline` | Boolean! | 指示用户可以在此资源上执行`destroy_pipeline` |
| `updatePipeline` | Boolean! | 指示用户可以对此资源执行`update_pipeline` |
## Project[](#project "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `alertManagementAlert` | AlertManagementAlert | 项目的单个警报管理警报 |
| `alertManagementAlertStatusCounts` | AlertManagementAlertStatusCountsType | 按项目状态的警报计数 |
| `allowMergeOnSkippedPipeline` | Boolean | 如果`only_allow_merge_if_pipeline_succeeds`为 true,则指示是否还可以将项目的合并请求与跳过的作业合并 |
| `archived` | Boolean | 指示项目的存档状态 |
| `autocloseReferencedIssues` | Boolean | 指示是否自动关闭默认分支中的合并请求和提交引用的问题 |
| `avatarUrl` | String | 项目头像图像文件的 URL |
| `board` | Board | 该项目的一块板 |
| `containerExpirationPolicy` | ContainerExpirationPolicy | 项目的集装箱过期政策 |
| `containerRegistryEnabled` | Boolean | 指示项目是否在容器注册表中存储 Docker 容器映像 |
| `createdAt` | Time | 项目创建的时间戳 |
| `description` | String | 项目简介 |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `forksCount` | Int! | 分叉项目的次数 |
| `fullPath` | ID! | 项目的完整路径 |
| `grafanaIntegration` | GrafanaIntegration | 该项目的 Grafana 集成详细信息 |
| `group` | Group | 项目组 |
| `httpUrlToRepo` | String | 通过 HTTPS 连接到项目的 URL |
| `id` | ID! | 项目编号 |
| `importStatus` | String | Status of import background job of the project |
| `issue` | Issue | 该项目的一期 |
| `issuesEnabled` | Boolean | 指示是否为当前用户启用了问题 |
| `jiraImportStatus` | String | 项目的 Jira 导入后台作业的状态 |
| `jobsEnabled` | Boolean | 指示是否为当前用户启用 CI / CD 管道作业 |
| `label` | Label | 此项目上可用的标签 |
| `lastActivityAt` | Time | 项目上次活动的时间戳 |
| `lfsEnabled` | Boolean | 指示项目是否启用了大文件存储(LFS) |
| `mergeRequest` | MergeRequest | 项目的单个合并请求 |
| `mergeRequestsEnabled` | Boolean | 指示是否为当前用户启用了合并请求 |
| `mergeRequestsFfOnlyEnabled` | Boolean | 指示是否不应该创建合并提交,而应该快速转发所有合并,这意味着仅当分支可以快速转发时才允许合并. |
| `name` | String! | 项目名称(无名称空间) |
| `nameWithNamespace` | String! | 项目的全名及其名称空间 |
| `namespace` | Namespace | 项目的命名空间 |
| `onlyAllowMergeIfAllDiscussionsAreResolved` | Boolean | 指示是否只有在解决所有讨论后才能合并项目的合并请求 |
| `onlyAllowMergeIfPipelineSucceeds` | Boolean | 指示项目的合并请求是否只能与成功的作业合并 |
| `openIssuesCount` | Int | 项目未解决的问题数 |
| `path` | String! | 项目路径 |
| `pipeline` | Pipeline | 建立项目管道 |
| `printingMergeRequestLinkEnabled` | Boolean | 指示从命令行推送到项目的 Git 存储库后是否显示用于创建或查看合并请求的链接 |
| `publicJobs` | Boolean | 指示是否可以公共访问项目的管道和作业详细信息,包括输出日志和工件 |
| `release` | Release | 该项目的一个版本 |
| `removeSourceBranchAfterMerge` | Boolean | 指示默认情况下是否应为项目的所有新合并请求启用" `Delete source branch`选项 |
| `repository` | Repository | 项目的 Git 存储库 |
| `requestAccessEnabled` | Boolean | 指示用户是否可以请求成员访问项目 |
| `requirement` | Requirement | 查找单个需求. 仅在启用功能标志`requirements_management`可用. |
| `requirementStatesCount` | RequirementStatesCount | 按状态列出的项目需求数量 |
| `sastCiConfiguration` | SastCiConfiguration | 项目的 SAST CI 配置 |
| `securityScanners` | SecurityScanners | 有关项目中使用的安全分析器的信息 |
| `sentryDetailedError` | SentryDetailedError | 该项目的 Sentry 错误的详细版本 |
| `sentryErrors` | SentryErrorCollection | 分批收集 Sentry 错误的项目 |
| `serviceDeskAddress` | String | 服务台的电子邮件地址. |
| `serviceDeskEnabled` | Boolean | 指示项目是否启用了服务台. |
| `sharedRunnersEnabled` | Boolean | 指示是否为项目启用了共享运行器 |
| `snippetsEnabled` | Boolean | 指示是否为当前用户启用了代码片段 |
| `sshUrlToRepo` | String | 通过 SSH 连接到项目的 URL |
| `starCount` | Int! | 已加注星标的次数 |
| `statistics` | ProjectStatistics | 项目统计 |
| `suggestionCommitMessage` | String | 用于应用合并请求建议的提交消息 |
| `tagList` | String | 项目主题列表(不是 Git 标签) |
| `userPermissions` | ProjectPermissions! | 当前用户对该资源的权限 |
| `visibility` | String | 项目的可见性 |
| `vulnerabilitySeveritiesCount` | VulnerabilitySeveritiesCount | 计算项目漏洞的每个严重程度 |
| `webUrl` | String | 项目的网址 |
| `wikiEnabled` | Boolean | 指示是否为当前用户启用了 Wiki |
## ProjectMember[](#projectmember "Permalink")
代表项目成员
| Name | Type | Description |
| --- | --- | --- |
| `accessLevel` | AccessLevel | GitLab ::访问级别 |
| `createdAt` | Time | 创建成员的日期和时间 |
| `createdBy` | User | 授权会员的用户 |
| `expiresAt` | Time | 成员资格到期的日期和时间 |
| `id` | ID! | 会员编号 |
| `project` | Project | 用户是其成员的项目 |
| `updatedAt` | Time | 成员的最新更新日期和时间 |
| `user` | User! | 与成员对象关联的用户 |
| `userPermissions` | ProjectPermissions! | 当前用户对该资源的权限 |
## ProjectPermissions[](#projectpermissions "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `adminOperations` | Boolean! | 指示用户可以对此资源执行`admin_operations` |
| `adminProject` | Boolean! | 指示用户可以对此资源执行`admin_project` |
| `adminRemoteMirror` | Boolean! | 指示用户可以对此资源执行`admin_remote_mirror` |
| `adminWiki` | Boolean! | 指示用户可以对此资源执行`admin_wiki` |
| `archiveProject` | Boolean! | 指示用户可以对此资源执行`archive_project` |
| `changeNamespace` | Boolean! | 指示用户可以在此资源上执行`change_namespace` |
| `changeVisibilityLevel` | Boolean! | 指示用户可以对此资源执行`change_visibility_level` |
| `createDeployment` | Boolean! | 指示用户可以对此资源执行`create_deployment` |
| `createDesign` | Boolean! | 指示用户可以对此资源执行`create_design` |
| `createIssue` | Boolean! | 指示用户可以对此资源执行`create_issue` |
| `createLabel` | Boolean! | 指示用户可以在此资源上执行`create_label` |
| `createMergeRequestFrom` | Boolean! | 指示用户可以在此资源上执行`create_merge_request_from` |
| `createMergeRequestIn` | Boolean! | 指示用户可以在此资源上执行`create_merge_request_in` |
| `createPages` | Boolean! | 指示用户可以在此资源上执行`create_pages` |
| `createPipeline` | Boolean! | Indicates the user can perform `create_pipeline` on this resource |
| `createPipelineSchedule` | Boolean! | 指示用户可以对此资源执行`create_pipeline_schedule` |
| `createSnippet` | Boolean! | 指示用户可以对此资源执行`create_snippet` |
| `createWiki` | Boolean! | 指示用户可以在此资源上执行`create_wiki` |
| `destroyDesign` | Boolean! | 指示用户可以对此资源执行`destroy_design` |
| `destroyPages` | Boolean! | 指示用户可以在此资源上执行`destroy_pages` |
| `destroyWiki` | Boolean! | 指示用户可以对此资源执行`destroy_wiki` |
| `downloadCode` | Boolean! | 指示用户可以对此资源执行`download_code` |
| `downloadWikiCode` | Boolean! | 指示用户可以在此资源上执行`download_wiki_code` |
| `forkProject` | Boolean! | 指示用户可以对此资源执行`fork_project` |
| `pushCode` | Boolean! | 指示用户可以对此资源执行`push_code` |
| `pushToDeleteProtectedBranch` | Boolean! | 指示用户可以对此资源执行`push_to_delete_protected_branch` |
| `readCommitStatus` | Boolean! | 指示用户可以对此资源执行`read_commit_status` |
| `readCycleAnalytics` | Boolean! | 指示用户可以对此资源执行`read_cycle_analytics` |
| `readDesign` | Boolean! | 指示用户可以对此资源执行`read_design` |
| `readMergeRequest` | Boolean! | 指示用户可以对此资源执行`read_merge_request` |
| `readPagesContent` | Boolean! | 指示用户可以对此资源执行`read_pages_content` |
| `readProject` | Boolean! | 指示用户可以对此资源执行`read_project` |
| `readProjectMember` | Boolean! | 指示用户可以对此资源执行`read_project_member` |
| `readWiki` | Boolean! | 指示用户可以对此资源执行`read_wiki` |
| `removeForkProject` | Boolean! | 指示用户可以对此资源执行`remove_fork_project` |
| `removePages` | Boolean! | 指示用户可以对此资源执行`remove_pages` |
| `removeProject` | Boolean! | 指示用户可以对此资源执行`remove_project` |
| `renameProject` | Boolean! | 指示用户可以对此资源执行`rename_project` |
| `requestAccess` | Boolean! | 指示用户可以对此资源执行`request_access` |
| `updatePages` | Boolean! | 指示用户可以对此资源执行`update_pages` |
| `updateWiki` | Boolean! | 指示用户可以对此资源执行`update_wiki` |
| `uploadFile` | Boolean! | 指示用户可以在此资源上执行`upload_file` |
## ProjectStatistics[](#projectstatistics "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `buildArtifactsSize` | Float! | 构建项目的工件大小 |
| `commitCount` | Float! | 提交项目数 |
| `lfsObjectsSize` | Float! | 项目的大文件存储(LFS)对象大小 |
| `packagesSize` | Float! | 项目包装尺寸 |
| `repositorySize` | Float! | 项目的存储库大小 |
| `snippetsSize` | Float | 项目片段大小 |
| `storageSize` | Float! | 项目的存储大小 |
| `wikiSize` | Float | 项目的 Wiki 大小 |
## Release[](#release "Permalink")
代表发行
| Name | Type | Description |
| --- | --- | --- |
| `assets` | ReleaseAssets | 发行资产 |
| `author` | User | 创建发布的用户 |
| `commit` | Commit | 与发布相关的提交 |
| `createdAt` | Time | 创建版本的时间戳 |
| `description` | String | 版本说明(也称为"发行说明") |
| `descriptionHtml` | String | The GitLab Flavored Markdown rendering of `description` |
| `links` | ReleaseLinks | 版本链接 |
| `name` | String | 发布名称 |
| `releasedAt` | Time | 发布版本的时间戳 |
| `tagName` | String | 与版本关联的标签名称 |
| `tagPath` | String | 与版本关联的标签的相对 Web 路径 |
## ReleaseAssetLink[](#releaseassetlink "Permalink")
表示与版本关联的资产链接
| Name | Type | Description |
| --- | --- | --- |
| `external` | Boolean | 表示链接指向外部资源 |
| `id` | ID! | 链接 ID |
| `linkType` | ReleaseAssetLinkType | 链接的类型: `other` , `runbook` , `image` , `package` ; 默认为`other` |
| `name` | String | Name of the link |
| `url` | String | 链接的 URL |
## ReleaseAssets[](#releaseassets "Permalink")
与发布相关的所有资产的容器
| Name | Type | Description |
| --- | --- | --- |
| `count` | Int | 发布的资产数量 |
## ReleaseEvidence[](#releaseevidence "Permalink")
释放证据
| Name | Type | Description |
| --- | --- | --- |
| `collectedAt` | Time | 证据收集的时间戳 |
| `filepath` | String | 可从中下载证据的 URL |
| `id` | ID! | 证据编号 |
| `sha` | String | 证据哈希的 SHA1 ID |
## ReleaseLinks[](#releaselinks "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `editUrl` | String | 版本的编辑页面的 HTTP URL |
| `issuesUrl` | String | 此版本过滤的问题页面的 HTTP URL |
| `mergeRequestsUrl` | String | 此版本过滤的合并请求页面的 HTTP URL |
| `selfUrl` | String | 版本的 HTTP URL |
## ReleaseSource[](#releasesource "Permalink")
表示特定格式附加到发行版的源代码
| Name | Type | Description |
| --- | --- | --- |
| `format` | String | 来源格式 |
| `url` | String | 源代码下载 URL |
## RemoveAwardEmojiPayload[](#removeawardemojipayload "Permalink")
自动生成的 RemoveAwardEmoji 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `awardEmoji` | AwardEmoji | 突变后的奖励表情符号 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## RemoveProjectFromSecurityDashboardPayload[](#removeprojectfromsecuritydashboardpayload "Permalink")
自动生成的 RemoveProjectFromSecurityDashboard 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## Repository[](#repository "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `empty` | Boolean! | 表示存储库中没有可见的内容 |
| `exists` | Boolean! | 表示磁盘上存在相应的 Git 存储库 |
| `rootRef` | String | 存储库的默认分支 |
| `tree` | Tree | 仓库的树 |
## Requirement[](#requirement "Permalink")
代表一个要求
| Name | Type | Description |
| --- | --- | --- |
| `author` | User! | 需求的作者 |
| `createdAt` | Time! | 创建需求的时间戳 |
| `id` | ID! | 需求 ID |
| `iid` | ID! | 需求的内部 ID |
| `project` | Project! | 需求所属的项目 |
| `state` | RequirementState! | 需求状态 |
| `title` | String | 要求的标题 |
| `updatedAt` | Time! | 上一次更新需求的时间戳 |
| `userPermissions` | RequirementPermissions! | 当前用户对该资源的权限 |
## RequirementPermissions[](#requirementpermissions "Permalink")
根据需要检查当前用户的权限
| Name | Type | Description |
| --- | --- | --- |
| `adminRequirement` | Boolean! | 指示用户可以对此资源执行`admin_requirement` |
| `createRequirement` | Boolean! | 指示用户可以对此资源执行`create_requirement` |
| `destroyRequirement` | Boolean! | 指示用户可以对此资源执行`destroy_requirement` |
| `readRequirement` | Boolean! | 指示用户可以对此资源执行`read_requirement` |
| `updateRequirement` | Boolean! | 指示用户可以对此资源执行`update_requirement` |
## RequirementStatesCount[](#requirementstatescount "Permalink")
需求状态的计数.
| Name | Type | Description |
| --- | --- | --- |
| `archived` | Int | 已归档需求数 |
| `opened` | Int | 打开的需求数 |
## RootStorageStatistics[](#rootstoragestatistics "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `buildArtifactsSize` | Float! | CI 工件大小(以字节为单位) |
| `lfsObjectsSize` | Float! | LFS 对象大小(以字节为单位) |
| `packagesSize` | Float! | 包大小(以字节为单位) |
| `repositorySize` | Float! | Git 存储库大小(以字节为单位) |
| `snippetsSize` | Float! | 片段大小(以字节为单位) |
| `storageSize` | Float! | 总存储字节数 |
| `wikiSize` | Float! | Wiki 大小(以字节为单位) |
## RunDASTScanPayload[](#rundastscanpayload "Permalink")
自动生成的 RunDASTScan 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `pipelineUrl` | String | 创建的管道的 URL. |
## SastCiConfigurationAnalyzersEntity[](#sastciconfigurationanalyzersentity "Permalink")
代表 SAST CI 配置中的分析器实体
| Name | Type | Description |
| --- | --- | --- |
| `description` | String | 表单上显示的分析器描述. |
| `enabled` | Boolean | 指示是否启用分析仪. |
| `label` | String | 配置 UI 中使用的分析器标签. |
| `name` | String | 分析仪的名称. |
## SastCiConfigurationEntity[](#sastciconfigurationentity "Permalink")
代表 SAST CI 配置中的实体
| Name | Type | Description |
| --- | --- | --- |
| `defaultValue` | String | 如果值为空,则使用默认值. |
| `description` | String | 表单上显示的实体描述. |
| `field` | String | 实体的 CI 关键字. |
| `label` | String | 表单中使用的实体的标签. |
| `type` | String | 字段值的类型. |
| `value` | String | 实体的当前值. |
## SastCiConfigurationOptionsEntity[](#sastciconfigurationoptionsentity "Permalink")
代表 SAST CI 配置中选项的实体
| Name | Type | Description |
| --- | --- | --- |
| `label` | String | 期权实体的标签. |
| `value` | String | 期权实体的价值. |
## ScannedResource[](#scannedresource "Permalink")
表示通过安全扫描扫描的资源
| Name | Type | Description |
| --- | --- | --- |
| `requestMethod` | String | 用于访问 URL 的 HTTP 请求方法 |
| `url` | String | 扫描仪扫描的 URL |
## SecurityReportSummary[](#securityreportsummary "Permalink")
代表安全报告摘要
| Name | Type | Description |
| --- | --- | --- |
| `containerScanning` | SecurityReportSummarySection | container_scanning 扫描的汇总计数 |
| `coverageFuzzing` | SecurityReportSummarySection | coverage_fuzzing 扫描的总计数 |
| `dast` | SecurityReportSummarySection | Dast 扫描的累计计数 |
| `dependencyScanning` | SecurityReportSummarySection | dependency_scanning 扫描的汇总计数 |
| `sast` | SecurityReportSummarySection | sast 扫描的累计计数 |
| `secretDetection` | SecurityReportSummarySection | secret_detection 扫描的总计计数 |
## SecurityReportSummarySection[](#securityreportsummarysection "Permalink")
代表安全报告摘要的一部分
| Name | Type | Description |
| --- | --- | --- |
| `scannedResourcesCount` | Int | 扫描资源总数 |
| `scannedResourcesCsvPath` | String | 以 CSV 格式下载所有扫描资源的路径 |
| `vulnerabilitiesCount` | Int | 漏洞总数 |
## SecurityScanners[](#securityscanners "Permalink")
代表安全扫描器列表
| Name | Type | Description |
| --- | --- | --- |
| `available` | SecurityScannerType! =>数组 | 可用于项目的分析仪列表. |
| `enabled` | SecurityScannerType! =>数组 | 为项目启用的分析器列表. |
| `pipelineRun` | SecurityScannerType! => Array | 在最新管道中成功运行的分析仪列表. |
## SentryDetailedError[](#sentrydetailederror "Permalink")
哨兵错误.
| Name | Type | Description |
| --- | --- | --- |
| `count` | Int! | 发生次数 |
| `culprit` | String! | 错误的罪魁祸首 |
| `externalBaseUrl` | String! | Sentry 实例的外部基本 URL |
| `externalUrl` | String! | 错误的外部网址 |
| `firstReleaseLastCommit` | String | 提交错误是第一次被发现 |
| `firstReleaseShortVersion` | String | 发布简短版本错误首次被发现 |
| `firstReleaseVersion` | String | 发布版本错误首次被发现 |
| `firstSeen` | Time! | 首次发现错误的时间戳 |
| `frequency` | SentryErrorFrequency! =>数组 | 最近 24 小时的错误统计信息 |
| `gitlabCommit` | String | 基于发行版的 GitLab 提交 SHA 归因于 Error |
| `gitlabCommitPath` | String | 错误归因于 GitLab 提交的 GitLab 页面的路径 |
| `gitlabIssuePath` | String | GitLab 问题的网址 |
| `id` | ID! | ID (global ID) of the error |
| `lastReleaseLastCommit` | String | 提交错误最后一次出现 |
| `lastReleaseShortVersion` | String | 发布简短版本错误最后一次出现 |
| `lastReleaseVersion` | String | 发布版本错误最后一次出现 |
| `lastSeen` | Time! | 上次出现错误的时间戳 |
| `message` | String | 错误的哨兵元数据消息 |
| `sentryId` | String! | 错误的 ID(哨兵 ID) |
| `sentryProjectId` | ID! | 项目的 ID(哨兵项目) |
| `sentryProjectName` | String! | 受错误影响的项目名称 |
| `sentryProjectSlug` | String! | 错误造成的项目影响 |
| `shortId` | String! | 错误的简称(Sentry ID) |
| `status` | SentryErrorStatus! | 错误状态 |
| `tags` | SentryErrorTags! | 与哨兵错误相关的标签 |
| `title` | String! | 错误标题 |
| `type` | String! | 错误类型 |
| `userCount` | Int! | 受错误影响的用户数 |
## SentryError[](#sentryerror "Permalink")
哨兵错误. SentryDetailedError 的简化版本.
| Name | Type | Description |
| --- | --- | --- |
| `count` | Int! | 发生次数 |
| `culprit` | String! | 错误的罪魁祸首 |
| `externalUrl` | String! | 错误的外部网址 |
| `firstSeen` | Time! | 首次发现错误的时间戳 |
| `frequency` | SentryErrorFrequency! =>数组 | 最近 24 小时的错误统计信息 |
| `id` | ID! | 错误的 ID(全局 ID) |
| `lastSeen` | Time! | 上次出现错误的时间戳 |
| `message` | String | 错误的哨兵元数据消息 |
| `sentryId` | String! | 错误的 ID(哨兵 ID) |
| `sentryProjectId` | ID! | 项目的 ID(哨兵项目) |
| `sentryProjectName` | String! | 受错误影响的项目名称 |
| `sentryProjectSlug` | String! | 错误造成的项目影响 |
| `shortId` | String! | 错误的简称(Sentry ID) |
| `status` | SentryErrorStatus! | 错误状态 |
| `title` | String! | 错误标题 |
| `type` | String! | 错误类型 |
| `userCount` | Int! | 受错误影响的用户数 |
## SentryErrorCollection[](#sentryerrorcollection "Permalink")
包含 Sentry 错误和详细错误的集合的对象.
| Name | Type | Description |
| --- | --- | --- |
| `detailedError` | SentryDetailedError | 该项目的 Sentry 错误的详细版本 |
| `errorStackTrace` | SentryErrorStackTrace | 哨兵错误的堆栈跟踪 |
| `errors` | SentryErrorConnection | 哨兵错误的收集 |
| `externalUrl` | String | 哨兵的外部网址 |
## SentryErrorFrequency[](#sentryerrorfrequency "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `count` | Int! | 自先前记录的时间以来收到的错误计数 |
| `time` | Time! | 记录错误频率统计信息的时间 |
## SentryErrorStackTrace[](#sentryerrorstacktrace "Permalink")
包含用于 Sentry 错误的堆栈跟踪条目的对象.
| Name | Type | Description |
| --- | --- | --- |
| `dateReceived` | String! | Sentry 收到堆栈跟踪的时间 |
| `issueId` | String! | Sentry 错误的 ID |
| `stackTraceEntries` | SentryErrorStackTraceEntry! =>数组 | 堆栈跟踪条目的 Sentry 错误 |
## SentryErrorStackTraceContext[](#sentryerrorstacktracecontext "Permalink")
Sentry 错误堆栈跟踪的对象上下文
| Name | Type | Description |
| --- | --- | --- |
| `code` | String! | 上下文的代码号 |
| `line` | Int! | 上下文的行号 |
## SentryErrorStackTraceEntry[](#sentryerrorstacktraceentry "Permalink")
包含用于 Sentry 错误的堆栈跟踪条目的对象.
| Name | Type | Description |
| --- | --- | --- |
| `col` | String | 发生哨兵错误的功能 |
| `fileName` | String | 发生 Sentry 错误的文件 |
| `function` | String | 发生哨兵错误的功能 |
| `line` | String | 发生哨兵错误的功能 |
| `traceContext` | SentryErrorStackTraceContext! =>数组 | Sentry 错误的上下文 |
## SentryErrorTags[](#sentryerrortags "Permalink")
哨兵状态错误
| Name | Type | Description |
| --- | --- | --- |
| `level` | String | 哨兵错误的严重程度 |
| `logger` | String | 哨兵记录仪错误 |
## Snippet[](#snippet "Permalink")
代表代码段条目
| Name | Type | Description |
| --- | --- | --- |
| `author` | User | 摘要的所有者 |
| `blob` | SnippetBlob! | 摘要片段 |
| `blobs` | SnippetBlob! =>数组 | 摘要片段 |
| `createdAt` | Time! | 创建此片段的时间戳 |
| `description` | String | 片段说明 |
| `descriptionHtml` | String | GitLab 风味 Markdown 渲染`description` |
| `fileName` | String | 片段的文件名 |
| `httpUrlToRepo` | String | 片段存储库的 HTTP URL |
| `id` | ID! | 摘要的 ID |
| `project` | Project | 代码段与之关联的项目 |
| `rawUrl` | String! | 代码段的原始 URL |
| `sshUrlToRepo` | String | 到代码段存储库的 SSH URL |
| `title` | String! | 摘要标题 |
| `updatedAt` | Time! | 此代码段的时间戳已更新 |
| `userPermissions` | SnippetPermissions! | 当前用户对该资源的权限 |
| `visibilityLevel` | VisibilityLevelsEnum! | 摘要的可见度级别 |
| `webUrl` | String! | 代码段的网址 |
## SnippetBlob[](#snippetblob "Permalink")
代表代码段 Blob
| Name | Type | Description |
| --- | --- | --- |
| `binary` | Boolean! | 显示 Blob 是否为二进制 |
| `externalStorage` | String | Blob 外部存储 |
| `mode` | String | 斑点模式 |
| `name` | String | Blob 名称 |
| `path` | String | 斑点路径 |
| `plainData` | String | Blob 普通高亮数据 |
| `rawPath` | String! | Blob 原始内容端点路径 |
| `renderedAsText` | Boolean! | 显示 Blob 是否呈现为文本 |
| `richData` | String | Blob 高亮显示的数据 |
| `richViewer` | SnippetBlobViewer | Blob 内容丰富的查看器 |
| `simpleViewer` | SnippetBlobViewer! | Blob 内容简单查看器 |
| `size` | Int! | 斑点大小 |
## SnippetBlobViewer[](#snippetblobviewer "Permalink")
表示应如何显示 Blob 内容
| Name | Type | Description |
| --- | --- | --- |
| `collapsed` | Boolean! | 显示是否应折叠显示 Blob |
| `fileType` | String! | 内容文件类型 |
| `loadAsync` | Boolean! | 显示 blob 内容是否异步加载 |
| `loadingPartialName` | String! | 载入部分名称 |
| `renderError` | String | 呈现 Blob 内容时出错 |
| `tooLarge` | Boolean! | 显示斑点是否太大而无法显示 |
| `type` | BlobViewersType! | Blob 查看器类型 |
## SnippetPermissions[](#snippetpermissions "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `adminSnippet` | Boolean! | 指示用户可以对此资源执行`admin_snippet` |
| `awardEmoji` | Boolean! | 表示用户可以在此资源上执行`award_emoji` |
| `createNote` | Boolean! | 指示用户可以在此资源上执行`create_note` |
| `readSnippet` | Boolean! | 指示用户可以对此资源执行`read_snippet` |
| `reportSnippet` | Boolean! | 指示用户可以对此资源执行`report_snippet` |
| `updateSnippet` | Boolean! | 指示用户可以对此资源执行`update_snippet` |
## Submodule[](#submodule "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `flatPath` | String! | 条目的平坦路径 |
| `id` | ID! | 条目 ID |
| `name` | String! | 条目名称 |
| `path` | String! | 条目路径 |
| `sha` | String! | 提交的最后提交 sha |
| `treeUrl` | String | 子模块的树 URL |
| `type` | EntryType! | 树条目的类型 |
| `webUrl` | String | 子模块的 Web URL |
## TaskCompletionStatus[](#taskcompletionstatus "Permalink")
任务的完成状态
| Name | Type | Description |
| --- | --- | --- |
| `completedCount` | Int! | 完成的任务数 |
| `count` | Int! | 总任务数 |
## TestReport[](#testreport "Permalink")
表示需求测试报告.
| Name | Type | Description |
| --- | --- | --- |
| `author` | User | 测试报告的作者 |
| `createdAt` | Time! | 创建测试报告的时间戳 |
| `id` | ID! | 测试报告编号 |
| `state` | TestReportState! | 测试报告的状态 |
## Timelog[](#timelog "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `date` | Time! | **不推荐使用:**使用`spentAt` . 在 12.10 中弃用 |
| `issue` | Issue | 记录时间已添加到的问题 |
| `spentAt` | Time | 跟踪时间的时间戳记 |
| `timeSpent` | Int! | 显示的时间(以秒为单位) |
| `user` | User! | 记录时间的用户 |
## Todo[](#todo "Permalink")
代表待办事项
| Name | Type | Description |
| --- | --- | --- |
| `action` | TodoActionEnum! | 待办事项的动作 |
| `author` | User! | 此待办事项的所有者 |
| `body` | String! | 待办事项的正文 |
| `createdAt` | Time! | 待办事项的时间戳记已创建 |
| `group` | Group | 与该待办事项相关的组 |
| `id` | ID! | 待办事项编号 |
| `project` | Project | 此待办事项与之相关的项目 |
| `state` | TodoStateEnum! | 待办事项的状态 |
| `targetType` | TodoTargetEnum! | 待办事项的目标类型 |
## TodoMarkDonePayload[](#todomarkdonepayload "Permalink")
自动生成的 TodoMarkDone 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `todo` | Todo! | 要求的待办事项 |
## TodoRestoreManyPayload[](#todorestoremanypayload "Permalink")
自动生成的 TodoRestoreMany 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `todos` | 一切! =>数组 | 全部更新 |
| `updatedIds` | ID! =>数组 | **不推荐使用:**使用待办事项. 在 13.2 中已弃用 |
## TodoRestorePayload[](#todorestorepayload "Permalink")
自动生成的 TodoRestore 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `todo` | Todo! | 要求的待办事项 |
## TodosMarkAllDonePayload[](#todosmarkalldonepayload "Permalink")
自动生成的 TodosMarkAllDone 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `todos` | 一切! =>数组 | 全部更新 |
| `updatedIds` | ID! =>数组 | **不推荐使用:**使用待办事项. 在 13.2 中已弃用 |
## ToggleAwardEmojiPayload[](#toggleawardemojipayload "Permalink")
自动生成的 ToggleAwardEmoji 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `awardEmoji` | AwardEmoji | 突变后的奖励表情符号 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `toggledOn` | Boolean! | 指示表情符号的状态. 如果切换开关授予表情符号,则为 true;如果切换开关删除了表情符号,则为 false. |
## Tree[](#tree "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `lastCommit` | Commit | 树的最后提交 |
## TreeEntry[](#treeentry "Permalink")
代表目录
| Name | Type | Description |
| --- | --- | --- |
| `flatPath` | String! | 条目的平坦路径 |
| `id` | ID! | 条目 ID |
| `name` | String! | 条目名称 |
| `path` | String! | 条目路径 |
| `sha` | String! | 提交的最后提交 sha |
| `type` | EntryType! | 树条目的类型 |
| `webUrl` | String | 树条目(目录)的 Web URL |
## UpdateAlertStatusPayload[](#updatealertstatuspayload "Permalink")
自动生成的 UpdateAlertStatus 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `alert` | AlertManagementAlert | 突变后的警报 |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后产生的问题 |
| `todo` | Todo | 突变后的待办事项 |
## UpdateContainerExpirationPolicyPayload[](#updatecontainerexpirationpolicypayload "Permalink")
自动生成的 UpdateContainerExpirationPolicy 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `containerExpirationPolicy` | ContainerExpirationPolicy | 变更后的容器到期政策 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## UpdateEpicPayload[](#updateepicpayload "Permalink")
自动生成的 UpdateEpic 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `epic` | Epic | 突变后的史诗 |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
## UpdateImageDiffNotePayload[](#updateimagediffnotepayload "Permalink")
自动生成的 UpdateImageDiffNote 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `note` | Note | 突变后的音符 |
## UpdateIssuePayload[](#updateissuepayload "Permalink")
自动生成的 UpdateIssue 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `issue` | Issue | 突变后的问题 |
## UpdateIterationPayload[](#updateiterationpayload "Permalink")
自动生成的 UpdateIteration 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `iteration` | Iteration | 更新的迭代 |
## UpdateNotePayload[](#updatenotepayload "Permalink")
自动生成的 UpdateNote 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `note` | Note | 突变后的音符 |
## UpdateRequirementPayload[](#updaterequirementpayload "Permalink")
自动生成的 UpdateRequirement 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `requirement` | Requirement | 突变后的要求 |
## UpdateSnippetPayload[](#updatesnippetpayload "Permalink")
自动生成的 UpdateSnippet 返回类型
| Name | Type | Description |
| --- | --- | --- |
| `clientMutationId` | String | 进行突变的客户的唯一标识符. |
| `errors` | 串! =>数组 | 执行突变期间遇到的错误. |
| `snippet` | Snippet | 突变后的代码段 |
## User[](#user "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `avatarUrl` | String | URL of the user’s avatar |
| `id` | ID! | 用户 ID |
| `name` | String! | 用户易读的名称 |
| `state` | UserState! | 用户状态 |
| `userPermissions` | UserPermissions! | 当前用户对该资源的权限 |
| `username` | String! | 用户的用户名. 在此 GitLab 实例中是唯一的 |
| `webUrl` | String! | 用户的网址 |
## UserPermissions[](#userpermissions "Permalink")
| Name | Type | Description |
| --- | --- | --- |
| `createSnippet` | Boolean! | 指示用户可以对此资源执行`create_snippet` |
## VulnerabilitiesCountByDayAndSeverity[](#vulnerabilitiescountbydayandseverity "Permalink")
表示在特定日期的特定严重性的漏洞数量
| Name | Type | Description |
| --- | --- | --- |
| `count` | Int | 漏洞数量 |
| `day` | ISO8601Date | 计数日期 |
| `severity` | VulnerabilitySeverity | 所计算漏洞的严重性 |
## Vulnerability[](#vulnerability "Permalink")
表示漏洞.
| Name | Type | Description |
| --- | --- | --- |
| `description` | String | 漏洞描述 |
| `id` | ID! | 漏洞的 GraphQL ID |
| `identifiers` | 漏洞标识符! =>数组 | 漏洞的标识符. |
| `location` | VulnerabilityLocation | 漏洞的位置元数据. 其字段取决于发现漏洞的安全扫描的类型 |
| `primaryIdentifier` | VulnerabilityIdentifier | 漏洞的主要标识符. |
| `project` | Project | 发现漏洞的项目 |
| `reportType` | VulnerabilityReportType | 发现漏洞的安全报告的类型(SAST,DEPENDENCY_SCANNING,CONTAINER_SCANNING,DAST,SECRET_DETECTION,COVERAGE_FUZZING) |
| `scanner` | VulnerabilityScanner | 漏洞的扫描程序元数据. |
| `severity` | VulnerabilitySeverity | 漏洞的严重程度(INFO,未知,LOW,MEDIUM,HIGH,CRITICAL) |
| `state` | VulnerabilityState | 漏洞状态(检测,已拒绝,已解决,已确认) |
| `title` | String | 漏洞标题 |
| `userNotesCount` | Int! | 漏洞附带的用户注释数 |
| `userPermissions` | VulnerabilityPermissions! | 当前用户对该资源的权限 |
| `vulnerabilityPath` | String | 漏洞详细信息页面的 URL |
## VulnerabilityIdentifier[](#vulnerabilityidentifier "Permalink")
表示漏洞标识符.
| Name | Type | Description |
| --- | --- | --- |
| `externalId` | String | 漏洞标识符的外部 ID |
| `externalType` | String | 漏洞标识符的外部类型 |
| `name` | String | 漏洞标识符的名称 |
| `url` | String | 漏洞标识符的 URL |
## VulnerabilityIssueLink[](#vulnerabilityissuelink "Permalink")
表示漏洞的问题链接.
| Name | Type | Description |
| --- | --- | --- |
| `id` | ID! | 漏洞的 GraphQL ID |
| `issue` | Issue! | 问题附在问题链接上 |
| `linkType` | VulnerabilityIssueLinkType! | 问题链接的类型 |
## VulnerabilityLocationContainerScanning[](#vulnerabilitylocationcontainerscanning "Permalink")
表示通过容器安全扫描发现的漏洞的位置
| Name | Type | Description |
| --- | --- | --- |
| `dependency` | VulnerableDependency | 包含漏洞的依赖项 |
| `image` | String | 易受攻击的容器映像的名称 |
| `operatingSystem` | String | 在易受攻击的容器映像上运行的操作系统 |
## VulnerabilityLocationDast[](#vulnerabilitylocationdast "Permalink")
表示通过 DAST 扫描发现的漏洞的位置
| Name | Type | Description |
| --- | --- | --- |
| `hostname` | String | 漏洞请求的域名 |
| `param` | String | 发生漏洞的 URL 的查询参数 |
| `path` | String | 漏洞请求的 URL 路径和查询字符串 |
| `requestMethod` | String | 易受攻击请求的 HTTP 方法 |
## VulnerabilityLocationDependencyScanning[](#vulnerabilitylocationdependencyscanning "Permalink")
表示依赖关系安全扫描发现的漏洞的位置
| Name | Type | Description |
| --- | --- | --- |
| `dependency` | VulnerableDependency | 包含漏洞的依赖项 |
| `file` | String | 易受攻击文件的路径 |
## VulnerabilityLocationSast[](#vulnerabilitylocationsast "Permalink")
表示通过 SAST 扫描发现的漏洞的位置
| Name | Type | Description |
| --- | --- | --- |
| `endLine` | String | 易受攻击的文件中最后相关的行号 |
| `file` | String | 易受攻击文件的路径 |
| `startLine` | String | 漏洞文件中第一相关行的编号 |
| `vulnerableClass` | String | 包含漏洞的类 |
| `vulnerableMethod` | String | 包含漏洞的方法 |
## VulnerabilityLocationSecretDetection[](#vulnerabilitylocationsecretdetection "Permalink")
表示通过秘密检测扫描发现的漏洞的位置
| Name | Type | Description |
| --- | --- | --- |
| `endLine` | String | 易受攻击的文件中最后相关的行号 |
| `file` | String | 易受攻击文件的路径 |
| `startLine` | String | 漏洞文件中第一相关行的编号 |
| `vulnerableClass` | String | 包含漏洞的类 |
| `vulnerableMethod` | String | 包含漏洞的方法 |
## VulnerabilityPermissions[](#vulnerabilitypermissions "Permalink")
检查当前用户对漏洞的权限
| Name | Type | Description |
| --- | --- | --- |
| `adminVulnerability` | Boolean! | 指示用户可以对此资源执行`admin_vulnerability` |
| `adminVulnerabilityIssueLink` | Boolean! | 指示用户可以对此资源执行`admin_vulnerability_issue_link` |
| `createVulnerability` | Boolean! | 指示用户可以对此资源执行`create_vulnerability` |
| `createVulnerabilityExport` | Boolean! | 指示用户可以对此资源执行`create_vulnerability_export` |
| `createVulnerabilityFeedback` | Boolean! | 指示用户可以对此资源执行`create_vulnerability_feedback` |
| `destroyVulnerabilityFeedback` | Boolean! | 指示用户可以对此资源执行`destroy_vulnerability_feedback` |
| `readVulnerabilityFeedback` | Boolean! | 指示用户可以对此资源执行`read_vulnerability_feedback` |
| `updateVulnerabilityFeedback` | Boolean! | 指示用户可以对此资源执行`update_vulnerability_feedback` |
## VulnerabilityScanner[](#vulnerabilityscanner "Permalink")
表示漏洞扫描程序.
| Name | Type | Description |
| --- | --- | --- |
| `externalId` | String | 漏洞扫描器的外部 ID |
| `name` | String | 漏洞扫描程序的名称 |
| `reportType` | VulnerabilityReportType | 漏洞报告的类型 |
| `vendor` | String | 漏洞扫描程序的供应商 |
## VulnerabilitySeveritiesCount[](#vulnerabilityseveritiescount "Permalink")
按严重性表示漏洞计数
| Name | Type | Description |
| --- | --- | --- |
| `critical` | Int | 项目严重程度的漏洞数量 |
| `high` | Int | 项目严重性高的漏洞数量 |
| `info` | Int | 项目的 INFO 严重性漏洞数量 |
| `low` | Int | 项目严重性为 LOW 的漏洞数量 |
| `medium` | Int | 项目 MEDIUM 严重程度的漏洞数量 |
| `unknown` | Int | 该项目严重程度未知的漏洞数量 |
## VulnerableDependency[](#vulnerabledependency "Permalink")
表示脆弱的依赖关系. 用于漏洞位置数据
| Name | Type | Description |
| --- | --- | --- |
| `package` | VulnerablePackage | 与弱势依赖项相关的软件包 |
| `version` | String | 脆弱依赖的版本 |
## VulnerablePackage[](#vulnerablepackage "Permalink")
表示易受攻击的程序包. 用于漏洞依赖性数据
| Name | Type | Description |
| --- | --- | --- |
| `name` | String | 易受攻击软件包的名称 |
- GitLab Docs
- Installation
- Requirements
- GitLab cloud native Helm Chart
- Install GitLab with Docker
- Installation from source
- Install GitLab on Microsoft Azure
- Installing GitLab on Google Cloud Platform
- Installing GitLab on Amazon Web Services (AWS)
- Analytics
- Code Review Analytics
- Productivity Analytics
- Value Stream Analytics
- Kubernetes clusters
- Adding and removing Kubernetes clusters
- Adding EKS clusters
- Adding GKE clusters
- Group-level Kubernetes clusters
- Instance-level Kubernetes clusters
- Canary Deployments
- Cluster Environments
- Deploy Boards
- GitLab Managed Apps
- Crossplane configuration
- Cluster management project (alpha)
- Kubernetes Logs
- Runbooks
- Serverless
- Deploying AWS Lambda function using GitLab CI/CD
- Securing your deployed applications
- Groups
- Contribution Analytics
- Custom group-level project templates
- Epics
- Manage epics
- Group Import/Export
- Insights
- Issues Analytics
- Iterations
- Public access
- SAML SSO for GitLab.com groups
- SCIM provisioning using SAML SSO for GitLab.com groups
- Subgroups
- Roadmap
- Projects
- GitLab Secure
- Security Configuration
- Container Scanning
- Dependency Scanning
- Dependency List
- Static Application Security Testing (SAST)
- Secret Detection
- Dynamic Application Security Testing (DAST)
- GitLab Security Dashboard
- Offline environments
- Standalone Vulnerability pages
- Security scanner integration
- Badges
- Bulk editing issues and merge requests at the project level
- Code Owners
- Compliance
- License Compliance
- Compliance Dashboard
- Create a project
- Description templates
- Deploy Keys
- Deploy Tokens
- File finder
- Project integrations
- Integrations
- Atlassian Bamboo CI Service
- Bugzilla Service
- Custom Issue Tracker service
- Discord Notifications service
- Enabling emails on push
- GitHub project integration
- Hangouts Chat service
- Atlassian HipChat
- Irker IRC Gateway
- GitLab Jira integration
- Mattermost Notifications Service
- Mattermost slash commands
- Microsoft Teams service
- Mock CI Service
- Prometheus integration
- Redmine Service
- Slack Notifications Service
- Slack slash commands
- GitLab Slack application
- Webhooks
- YouTrack Service
- Insights
- Issues
- Crosslinking Issues
- Design Management
- Confidential issues
- Due dates
- Issue Boards
- Issue Data and Actions
- Labels
- Managing issues
- Milestones
- Multiple Assignees for Issues
- Related issues
- Service Desk
- Sorting and ordering issue lists
- Issue weight
- Associate a Zoom meeting with an issue
- Merge requests
- Allow collaboration on merge requests across forks
- Merge Request Approvals
- Browser Performance Testing
- How to create a merge request
- Cherry-pick changes
- Code Quality
- Load Performance Testing
- Merge Request dependencies
- Fast-forward merge requests
- Merge when pipeline succeeds
- Merge request conflict resolution
- Reverting changes
- Reviewing and managing merge requests
- Squash and merge
- Merge requests versions
- Draft merge requests
- Members of a project
- Migrating projects to a GitLab instance
- Import your project from Bitbucket Cloud to GitLab
- Import your project from Bitbucket Server to GitLab
- Migrating from ClearCase
- Migrating from CVS
- Import your project from FogBugz to GitLab
- Gemnasium
- Import your project from GitHub to GitLab
- Project importing from GitLab.com to your private GitLab instance
- Import your project from Gitea to GitLab
- Import your Jira project issues to GitLab
- Migrating from Perforce Helix
- Import Phabricator tasks into a GitLab project
- Import multiple repositories by uploading a manifest file
- Import project from repo by URL
- Migrating from SVN to GitLab
- Migrating from TFVC to Git
- Push Options
- Releases
- Repository
- Branches
- Git Attributes
- File Locking
- Git file blame
- Git file history
- Repository mirroring
- Protected branches
- Protected tags
- Push Rules
- Reduce repository size
- Signing commits with GPG
- Syntax Highlighting
- GitLab Web Editor
- Web IDE
- Requirements Management
- Project settings
- Project import/export
- Project access tokens (Alpha)
- Share Projects with other Groups
- Snippets
- Static Site Editor
- Wiki
- Project operations
- Monitor metrics for your CI/CD environment
- Set up alerts for Prometheus metrics
- Embedding metric charts within GitLab-flavored Markdown
- Embedding Grafana charts
- Using the Metrics Dashboard
- Dashboard YAML properties
- Metrics dashboard settings
- Panel types for dashboards
- Using Variables
- Templating variables for metrics dashboards
- Prometheus Metrics library
- Monitoring AWS Resources
- Monitoring HAProxy
- Monitoring Kubernetes
- Monitoring NGINX
- Monitoring NGINX Ingress Controller
- Monitoring NGINX Ingress Controller with VTS metrics
- Alert Management
- Error Tracking
- Tracing
- Incident Management
- GitLab Status Page
- Feature Flags
- GitLab CI/CD
- GitLab CI/CD pipeline configuration reference
- GitLab CI/CD include examples
- Introduction to CI/CD with GitLab
- Getting started with GitLab CI/CD
- How to enable or disable GitLab CI/CD
- Using SSH keys with GitLab CI/CD
- Migrating from CircleCI
- Migrating from Jenkins
- Auto DevOps
- Getting started with Auto DevOps
- Requirements for Auto DevOps
- Customizing Auto DevOps
- Stages of Auto DevOps
- Upgrading PostgreSQL for Auto DevOps
- Cache dependencies in GitLab CI/CD
- GitLab ChatOps
- Cloud deployment
- Docker integration
- Building Docker images with GitLab CI/CD
- Using Docker images
- Building images with kaniko and GitLab CI/CD
- GitLab CI/CD environment variables
- Predefined environment variables reference
- Where variables can be used
- Deprecated GitLab CI/CD variables
- Environments and deployments
- Protected Environments
- GitLab CI/CD Examples
- Test a Clojure application with GitLab CI/CD
- Using Dpl as deployment tool
- Testing a Phoenix application with GitLab CI/CD
- End-to-end testing with GitLab CI/CD and WebdriverIO
- DevOps and Game Dev with GitLab CI/CD
- Deploy a Spring Boot application to Cloud Foundry with GitLab CI/CD
- How to deploy Maven projects to Artifactory with GitLab CI/CD
- Testing PHP projects
- Running Composer and NPM scripts with deployment via SCP in GitLab CI/CD
- Test and deploy Laravel applications with GitLab CI/CD and Envoy
- Test and deploy a Python application with GitLab CI/CD
- Test and deploy a Ruby application with GitLab CI/CD
- Test and deploy a Scala application to Heroku
- GitLab CI/CD for external repositories
- Using GitLab CI/CD with a Bitbucket Cloud repository
- Using GitLab CI/CD with a GitHub repository
- GitLab Pages
- GitLab Pages
- GitLab Pages domain names, URLs, and baseurls
- Create a GitLab Pages website from scratch
- Custom domains and SSL/TLS Certificates
- GitLab Pages integration with Let's Encrypt
- GitLab Pages Access Control
- Exploring GitLab Pages
- Incremental Rollouts with GitLab CI/CD
- Interactive Web Terminals
- Optimizing GitLab for large repositories
- Metrics Reports
- CI/CD pipelines
- Pipeline Architecture
- Directed Acyclic Graph
- Multi-project pipelines
- Parent-child pipelines
- Pipelines for Merge Requests
- Pipelines for Merged Results
- Merge Trains
- Job artifacts
- Pipeline schedules
- Pipeline settings
- Triggering pipelines through the API
- Review Apps
- Configuring GitLab Runners
- GitLab CI services examples
- Using MySQL
- Using PostgreSQL
- Using Redis
- Troubleshooting CI/CD
- GitLab Package Registry
- GitLab Container Registry
- Dependency Proxy
- GitLab Composer Repository
- GitLab Conan Repository
- GitLab Maven Repository
- GitLab NPM Registry
- GitLab NuGet Repository
- GitLab PyPi Repository
- API Docs
- API resources
- .gitignore API
- GitLab CI YMLs API
- Group and project access requests API
- Appearance API
- Applications API
- Audit Events API
- Avatar API
- Award Emoji API
- Project badges API
- Group badges API
- Branches API
- Broadcast Messages API
- Project clusters API
- Group clusters API
- Instance clusters API
- Commits API
- Container Registry API
- Custom Attributes API
- Dashboard annotations API
- Dependencies API
- Deploy Keys API
- Deployments API
- Discussions API
- Dockerfiles API
- Environments API
- Epics API
- Events
- Feature Flags API
- Feature flag user lists API
- Freeze Periods API
- Geo Nodes API
- Group Activity Analytics API
- Groups API
- Import API
- Issue Boards API
- Group Issue Boards API
- Issues API
- Epic Issues API
- Issues Statistics API
- Jobs API
- Keys API
- Labels API
- Group Labels API
- License
- Licenses API
- Issue links API
- Epic Links API
- Managed Licenses API
- Markdown API
- Group and project members API
- Merge request approvals API
- Merge requests API
- Project milestones API
- Group milestones API
- Namespaces API
- Notes API
- Notification settings API
- Packages API
- Pages domains API
- Pipeline schedules API
- Pipeline triggers API
- Pipelines API
- Project Aliases API
- Project import/export API
- Project repository storage moves API
- Project statistics API
- Project templates API
- Projects API
- Protected branches API
- Protected tags API
- Releases API
- Release links API
- Repositories API
- Repository files API
- Repository submodules API
- Resource label events API
- Resource milestone events API
- Resource weight events API
- Runners API
- SCIM API
- Search API
- Services API
- Application settings API
- Sidekiq Metrics API
- Snippets API
- Project snippets
- Application statistics API
- Suggest Changes API
- System hooks API
- Tags API
- Todos API
- Users API
- Project-level Variables API
- Group-level Variables API
- Version API
- Vulnerabilities API
- Vulnerability Findings API
- Wikis API
- GraphQL API
- Getting started with GitLab GraphQL API
- GraphQL API Resources
- API V3 to API V4
- Validate the .gitlab-ci.yml (API)
- User Docs
- Abuse reports
- User account
- Active sessions
- Deleting a User account
- Permissions
- Personal access tokens
- Profile preferences
- Threads
- GitLab and SSH keys
- GitLab integrations
- Git
- GitLab.com settings
- Infrastructure as code with Terraform and GitLab
- GitLab keyboard shortcuts
- GitLab Markdown
- AsciiDoc
- GitLab Notification Emails
- GitLab Quick Actions
- Autocomplete characters
- Reserved project and group names
- Search through GitLab
- Advanced Global Search
- Advanced Syntax Search
- Time Tracking
- GitLab To-Do List
- Administrator Docs
- Reference architectures
- Reference architecture: up to 1,000 users
- Reference architecture: up to 2,000 users
- Reference architecture: up to 3,000 users
- Reference architecture: up to 5,000 users
- Reference architecture: up to 10,000 users
- Reference architecture: up to 25,000 users
- Reference architecture: up to 50,000 users
- Troubleshooting a reference architecture set up
- Working with the bundled Consul service
- Configuring PostgreSQL for scaling
- Configuring GitLab application (Rails)
- Load Balancer for multi-node GitLab
- Configuring a Monitoring node for Scaling and High Availability
- NFS
- Working with the bundled PgBouncer service
- Configuring Redis for scaling
- Configuring Sidekiq
- Admin Area settings
- Continuous Integration and Deployment Admin settings
- Custom instance-level project templates
- Diff limits administration
- Enable and disable GitLab features deployed behind feature flags
- Geo nodes Admin Area
- GitLab Pages administration
- Health Check
- Job logs
- Labels administration
- Log system
- PlantUML & GitLab
- Repository checks
- Repository storage paths
- Repository storage types
- Account and limit settings
- Service templates
- System hooks
- Changing your time zone
- Uploads administration
- Abuse reports
- Activating and deactivating users
- Audit Events
- Blocking and unblocking users
- Broadcast Messages
- Elasticsearch integration
- Gitaly
- Gitaly Cluster
- Gitaly reference
- Monitoring GitLab
- Monitoring GitLab with Prometheus
- Performance Bar
- Usage statistics
- Object Storage
- Performing Operations in GitLab
- Cleaning up stale Redis sessions
- Fast lookup of authorized SSH keys in the database
- Filesystem Performance Benchmarking
- Moving repositories managed by GitLab
- Run multiple Sidekiq processes
- Sidekiq MemoryKiller
- Switching to Puma
- Understanding Unicorn and unicorn-worker-killer
- User lookup via OpenSSH's AuthorizedPrincipalsCommand
- GitLab Package Registry administration
- GitLab Container Registry administration
- Replication (Geo)
- Geo database replication
- Geo with external PostgreSQL instances
- Geo configuration
- Using a Geo Server
- Updating the Geo nodes
- Geo with Object storage
- Docker Registry for a secondary node
- Geo for multiple nodes
- Geo security review (Q&A)
- Location-aware Git remote URL with AWS Route53
- Tuning Geo
- Removing secondary Geo nodes
- Geo data types support
- Geo Frequently Asked Questions
- Geo Troubleshooting
- Geo validation tests
- Disaster Recovery (Geo)
- Disaster recovery for planned failover
- Bring a demoted primary node back online
- Automatic background verification
- Rake tasks
- Back up and restore GitLab
- Clean up
- Namespaces
- Maintenance Rake tasks
- Geo Rake Tasks
- GitHub import
- Import bare repositories
- Integrity check Rake task
- LDAP Rake tasks
- Listing repository directories
- Praefect Rake tasks
- Project import/export administration
- Repository storage Rake tasks
- Generate sample Prometheus data
- Uploads migrate Rake tasks
- Uploads sanitize Rake tasks
- User management
- Webhooks administration
- X.509 signatures
- Server hooks
- Static objects external storage
- Updating GitLab
- GitLab release and maintenance policy
- Security
- Password Storage
- Custom password length limits
- Restrict allowed SSH key technologies and minimum length
- Rate limits
- Webhooks and insecure internal web services
- Information exclusivity
- How to reset your root password
- How to unlock a locked user from the command line
- User File Uploads
- How we manage the TLS protocol CRIME vulnerability
- User email confirmation at sign-up
- Security of running jobs
- Proxying assets
- CI/CD Environment Variables
- Contributor and Development Docs
- Contribute to GitLab
- Community members & roles
- Implement design & UI elements
- Issues workflow
- Merge requests workflow
- Code Review Guidelines
- Style guides
- GitLab Architecture Overview
- CI/CD development documentation
- Database guides
- Database Review Guidelines
- Database Review Guidelines
- Migration Style Guide
- What requires downtime?
- Understanding EXPLAIN plans
- Rake tasks for developers
- Mass inserting Rails models
- GitLab Documentation guidelines
- Documentation Style Guide
- Documentation structure and template
- Documentation process
- Documentation site architecture
- Global navigation
- GitLab Docs monthly release process
- Telemetry Guide
- Usage Ping Guide
- Snowplow Guide
- Experiment Guide
- Feature flags in development of GitLab
- Feature flags process
- Developing with feature flags
- Feature flag controls
- Document features deployed behind feature flags
- Frontend Development Guidelines
- Accessibility & Readability
- Ajax
- Architecture
- Axios
- Design Patterns
- Frontend Development Process
- DropLab
- Emojis
- Filter
- Frontend FAQ
- GraphQL
- Icons and SVG Illustrations
- InputSetter
- Performance
- Principles
- Security
- Tooling
- Vuex
- Vue
- Geo (development)
- Geo self-service framework (alpha)
- Gitaly developers guide
- GitLab development style guides
- API style guide
- Go standards and style guidelines
- GraphQL API style guide
- Guidelines for shell commands in the GitLab codebase
- HTML style guide
- JavaScript style guide
- Migration Style Guide
- Newlines style guide
- Python Development Guidelines
- SCSS style guide
- Shell scripting standards and style guidelines
- Sidekiq debugging
- Sidekiq Style Guide
- SQL Query Guidelines
- Vue.js style guide
- Instrumenting Ruby code
- Testing standards and style guidelines
- Flaky tests
- Frontend testing standards and style guidelines
- GitLab tests in the Continuous Integration (CI) context
- Review Apps
- Smoke Tests
- Testing best practices
- Testing levels
- Testing Rails migrations at GitLab
- Testing Rake tasks
- End-to-end Testing
- Beginner's guide to writing end-to-end tests
- End-to-end testing Best Practices
- Dynamic Element Validation
- Flows in GitLab QA
- Page objects in GitLab QA
- Resource class in GitLab QA
- Style guide for writing end-to-end tests
- Testing with feature flags
- Translate GitLab to your language
- Internationalization for GitLab
- Translating GitLab
- Proofread Translations
- Merging translations from CrowdIn
- Value Stream Analytics development guide
- GitLab subscription
- Activate GitLab EE with a license