Skip to content
体验新版
项目
组织
正在加载...
登录
切换导航
打开侧边栏
李少辉-开发者
gitlab-foss
提交
59fdc168
G
gitlab-foss
项目概览
李少辉-开发者
/
gitlab-foss
通知
15
Star
0
Fork
0
代码
文件
提交
分支
Tags
贡献者
分支图
Diff
Issue
0
列表
看板
标记
里程碑
合并请求
0
Wiki
0
Wiki
分析
仓库
DevOps
项目成员
Pages
G
gitlab-foss
项目概览
项目概览
详情
发布
仓库
仓库
文件
提交
分支
标签
贡献者
分支图
比较
Issue
0
Issue
0
列表
看板
标记
里程碑
合并请求
0
合并请求
0
Pages
分析
分析
仓库分析
DevOps
Wiki
0
Wiki
成员
成员
收起侧边栏
关闭侧边栏
动态
分支图
创建新Issue
提交
Issue看板
体验新版 GitCode,发现更多精彩内容 >>
提交
59fdc168
编写于
7月 30, 2018
作者:
J
Jan Beckmann
提交者:
Rémy Coutable
7月 30, 2018
浏览文件
操作
浏览文件
下载
电子邮件补丁
差异文件
Resolve "Merge Request API response is missing changes_count"
上级
87f03f01
变更
2
显示空白变更内容
内联
并排
Showing
2 changed file
with
10 addition
and
12 deletion
+10
-12
changelogs/unreleased/47728-mr-api-documentation-changes.yml
changelogs/unreleased/47728-mr-api-documentation-changes.yml
+5
-0
doc/api/merge_requests.md
doc/api/merge_requests.md
+5
-12
未找到文件。
changelogs/unreleased/47728-mr-api-documentation-changes.yml
0 → 100644
浏览文件 @
59fdc168
---
title
:
Remove changes_count from MR API documentation where necessary
merge_request
:
19745
author
:
Jan Beckmann
type
:
fixed
doc/api/merge_requests.md
浏览文件 @
59fdc168
...
@@ -15,11 +15,6 @@ given state (`opened`, `closed`, `locked`, or `merged`) or all of them (`all`).
...
@@ -15,11 +15,6 @@ given state (`opened`, `closed`, `locked`, or `merged`) or all of them (`all`).
The pagination parameters
`page`
and
`per_page`
can be used to
The pagination parameters
`page`
and
`per_page`
can be used to
restrict the list of merge requests.
restrict the list of merge requests.
**Note**
: the
`changes_count`
value in the response is a string, not an
integer. This is because when an MR has too many changes to display and store,
it will be capped at 1,000. In that case, the API will return the string
`"1000+"`
for the changes count.
```
```
GET /merge_requests
GET /merge_requests
GET /merge_requests?state=opened
GET /merge_requests?state=opened
...
@@ -104,7 +99,6 @@ Parameters:
...
@@ -104,7 +99,6 @@ Parameters:
"sha"
:
"8888888888888888888888888888888888888888"
,
"sha"
:
"8888888888888888888888888888888888888888"
,
"merge_commit_sha"
:
null
,
"merge_commit_sha"
:
null
,
"user_notes_count"
:
1
,
"user_notes_count"
:
1
,
"changes_count"
:
"1"
,
"should_remove_source_branch"
:
true
,
"should_remove_source_branch"
:
true
,
"force_remove_source_branch"
:
false
,
"force_remove_source_branch"
:
false
,
"squash"
:
false
,
"squash"
:
false
,
...
@@ -144,10 +138,6 @@ will be the same. In the case of a merge request from a fork,
...
@@ -144,10 +138,6 @@ will be the same. In the case of a merge request from a fork,
`target_project_id`
and
`project_id`
will be the same and
`target_project_id`
and
`project_id`
will be the same and
`source_project_id`
will be the fork project's ID.
`source_project_id`
will be the fork project's ID.
**Note**
: the
`changes_count`
value in the response is a string, not an
integer. This is because when an MR has too many changes to display and store,
it will be capped at 1,000. In that case, the API will return the string
`"1000+"`
for the changes count.
Parameters:
Parameters:
...
@@ -224,7 +214,6 @@ Parameters:
...
@@ -224,7 +214,6 @@ Parameters:
"sha"
:
"8888888888888888888888888888888888888888"
,
"sha"
:
"8888888888888888888888888888888888888888"
,
"merge_commit_sha"
:
null
,
"merge_commit_sha"
:
null
,
"user_notes_count"
:
1
,
"user_notes_count"
:
1
,
"changes_count"
:
"1"
,
"should_remove_source_branch"
:
true
,
"should_remove_source_branch"
:
true
,
"force_remove_source_branch"
:
false
,
"force_remove_source_branch"
:
false
,
"squash"
:
false
,
"squash"
:
false
,
...
@@ -331,7 +320,6 @@ Parameters:
...
@@ -331,7 +320,6 @@ Parameters:
"sha"
:
"8888888888888888888888888888888888888888"
,
"sha"
:
"8888888888888888888888888888888888888888"
,
"merge_commit_sha"
:
null
,
"merge_commit_sha"
:
null
,
"user_notes_count"
:
1
,
"user_notes_count"
:
1
,
"changes_count"
:
"1"
,
"should_remove_source_branch"
:
true
,
"should_remove_source_branch"
:
true
,
"force_remove_source_branch"
:
false
,
"force_remove_source_branch"
:
false
,
"web_url"
:
"http://example.com/example/example/merge_requests/1"
,
"web_url"
:
"http://example.com/example/example/merge_requests/1"
,
...
@@ -350,6 +338,11 @@ Parameters:
...
@@ -350,6 +338,11 @@ Parameters:
Shows information about a single merge request.
Shows information about a single merge request.
**Note**
: the
`changes_count`
value in the response is a string, not an
integer. This is because when an MR has too many changes to display and store,
it will be capped at 1,000. In that case, the API will return the string
`"1000+"`
for the changes count.
```
```
GET /projects/:id/merge_requests/:merge_request_iid
GET /projects/:id/merge_requests/:merge_request_iid
```
```
...
...
编辑
预览
Markdown
is supported
0%
请重试
或
添加新附件
.
添加附件
取消
You are about to add
0
people
to the discussion. Proceed with caution.
先完成此消息的编辑!
取消
想要评论请
注册
或
登录