GitLab Api使用

博主： F嘉阳
发布时间：2019 年 11 月 06 日
1196 次浏览
暂无评论
11141字数
分类：开发

使用场景

为了进行规范化配置管理工作，基于gitlab规范分支管理流程，经常需要新建分支、设置保护分支和操作分支封板等，若只有几个工程则直接在gitlab web界面上操作即可，一旦工程数量增多，则会消耗大量时间，故考虑可通过gitlab 提供的web api编写脚本进行自动化操作

Api指南

此处摘要部分官网API文档指南，所有api操作都需要在gitlab上申请访问令牌，该令牌应当至少包含api访问权限

获取工程列表

支持多种参数过滤，非必传

Get a list of all visible projects across GitLab for the authenticated user. When accessed without authentication, only public projects with “simple” fields are returned.
GET /projects
Attribute Type Required Description

archived boolean no Limit by archived status

visibility string no Limit by visibility public, internal, or private

order_by string no Return projects ordered by id, name, path, created_at, updated_at, or last_activity_at fields. Default is created_at

sort string no Return projects sorted in asc or desc order. Default is desc

search string no Return list of projects matching the search criteria

simple boolean no Return only limited fields for each project. This is a no-op without authentication as then only simple fields are returned.

owned boolean no Limit by projects explicitly owned by the current user

membership boolean no Limit by projects that the current user is a member of

starred boolean no Limit by projects starred by the current user

statistics boolean no Include project statistics

with_custom_attributes boolean no Include custom attributes in response (admins only)

with_issues_enabled boolean no Limit by enabled issues feature

with_merge_requests_enabled boolean no Limit by enabled merge requests feature

with_programming_language string no Limit by projects which use the given programming language

wiki_checksum_failed boolean no Limit projects where the wiki checksum calculation has failed (Introduced in GitLab Premium 11.2)

repository_checksum_failed boolean no Limit projects where the repository checksum calculation has failed (Introduced in GitLab Premium 11.2)

min_access_level integer no Limit by current user minimal access level

Attribute	Type	Required	Description
`archived`	boolean	no	Limit by archived status
`visibility`	string	no	Limit by visibility `public`, `internal`, or `private`
`order_by`	string	no	Return projects ordered by `id`, `name`, `path`, `created_at`, `updated_at`, or `last_activity_at` fields. Default is `created_at`
`sort`	string	no	Return projects sorted in `asc` or `desc` order. Default is `desc`
`search`	string	no	Return list of projects matching the search criteria
`simple`	boolean	no	Return only limited fields for each project. This is a no-op without authentication as then only simple fields are returned.
`owned`	boolean	no	Limit by projects explicitly owned by the current user
`membership`	boolean	no	Limit by projects that the current user is a member of
`starred`	boolean	no	Limit by projects starred by the current user
`statistics`	boolean	no	Include project statistics
`with_custom_attributes`	boolean	no	Include custom attributes in response (admins only)
`with_issues_enabled`	boolean	no	Limit by enabled issues feature
`with_merge_requests_enabled`	boolean	no	Limit by enabled merge requests feature
`with_programming_language`	string	no	Limit by projects which use the given programming language
`wiki_checksum_failed`	boolean	no	Limit projects where the wiki checksum calculation has failed (Introduced in GitLab Premium 11.2)
`repository_checksum_failed`	boolean	no	Limit projects where the repository checksum calculation has failed (Introduced in GitLab Premium 11.2)
`min_access_level`	integer	no	Limit by current user minimal access level

分支操作

文档地址

创建分支

需要传递仓库ID、源分支名、新分支名称

Create a new branch in the repository.
POST /projects/:id/repository/branches
Parameters:

Attribute Type Required Description

id integer yes ID or URL-encoded path of the project owned by the authenticated user.

branch string yes Name of the branch.

ref string yes Branch name or commit SHA to create branch from.

Example request:
curl --request POST --header "PRIVATE-TOKEN: " https://gitlab.example.com/api/v4/projects/5/repository/branches?branch=newbranch&ref=master

Attribute	Type	Required	Description
`id`	integer	yes	ID or URL-encoded path of the project owned by the authenticated user.
`branch`	string	yes	Name of the branch.
`ref`	string	yes	Branch name or commit SHA to create branch from.

保护分支

分支保护等级说明

Valid access levels

The access levels are defined in the ProtectedRefAccess.allowed_access_levels method. Currently, these levels are recognized:
0  => No access
30 => Developer access
40 => Maintainer access
60 => Admin access

需要传递分支名称、访问级别等信息

Protects a single repository branch or several project repository branches using a wildcard protected branch.
POST /projects/:id/protected_branches
curl --request POST --header "PRIVATE-TOKEN: " 'https://gitlab.example.com/api/v4/projects/5/protected_branches?name=*-stable&push_access_level=30&merge_access_level=30&unprotect_access_level=40'
Attribute Type Required Description

id integer/string yes The ID or URL-encoded path of the project owned by the authenticated user

name string yes The name of the branch or wildcard

push_access_level string no Access levels allowed to push (defaults: 40, maintainer access level)

merge_access_level string no Access levels allowed to merge (defaults: 40, maintainer access level)

unprotect_access_level string no Access levels allowed to unprotect (defaults: 40, maintainer access level)

allowed_to_push array no Array of access levels allowed to push, with each described by a hash

allowed_to_merge array no Array of access levels allowed to merge, with each described by a hash

allowed_to_unprotect array no Array of access levels allowed to unprotect, with each described by a hash

code_owner_approval_required boolean no Prevent pushes to this branch if it matches an item in the CODEOWNERS file. (defaults: false)

Attribute	Type	Required	Description
`id`	integer/string	yes	The ID or URL-encoded path of the project owned by the authenticated user
`name`	string	yes	The name of the branch or wildcard
`push_access_level`	string	no	Access levels allowed to push (defaults: `40`, maintainer access level)
`merge_access_level`	string	no	Access levels allowed to merge (defaults: `40`, maintainer access level)
`unprotect_access_level`	string	no	Access levels allowed to unprotect (defaults: `40`, maintainer access level)
`allowed_to_push`	array	no	Array of access levels allowed to push, with each described by a hash
`allowed_to_merge`	array	no	Array of access levels allowed to merge, with each described by a hash
`allowed_to_unprotect`	array	no	Array of access levels allowed to unprotect, with each described by a hash
`code_owner_approval_required`	boolean	no	Prevent pushes to this branch if it matches an item in the `CODEOWNERS` file. (defaults: false)

取消保护分支

需要传递仓库ID、分支名称

Unprotects the given protected branch or wildcard protected branch.
DELETE /projects/:id/protected_branches/:name
curl --request DELETE --header "PRIVATE-TOKEN: " 'https://gitlab.example.com/api/v4/projects/5/protected_branches/*-stable'
Attribute Type Required Description

id integer/string yes The ID or URL-encoded path of the project owned by the authenticated user

name string yes The name of the branch

Attribute	Type	Required	Description
`id`	integer/string	yes	The ID or URL-encoded path of the project owned by the authenticated user
`name`	string	yes	The name of the branch

删除分支

需要传递仓库ID和分支名称

Delete a branch from the repository.

Note: In the case of an error, an explanation message is provided.
DELETE /projects/:id/repository/branches/:branch
Parameters:

Attribute Type Required Description

id integer/string yes ID or URL-encoded path of the project owned by the authenticated user.

branch string yes Name of the branch.

Example request:
curl --request DELETE --header "PRIVATE-TOKEN: " https://gitlab.example.com/api/v4/projects/5/repository/branches/newbranch

Attribute	Type	Required	Description
`id`	integer/string	yes	ID or URL-encoded path of the project owned by the authenticated user.
`branch`	string	yes	Name of the branch.

接口测试

使用postman对接口进行测试

获取工程列表

通过该接口可以查询所有工程的ID，注意，该接口默认使用了分页

脚本编写

批量创建分支

定义工程ID数组，对数组进行遍历，并设置基础分支变量，方便调整，此处默认写死基础分支，有需要也可以通过变量传递

#!/usr/bin/env bash

# 访问令牌
PRIVATE_TOKEN="XXXX"
# 分支名称
branch_name=$1

base_branch="BasicBranch"

# 项目ID
projectids=(47 48 50 51 52 54 55 56 58 59 60 62 63 64 65 67 68 69 70 71 74 75 89 90 91 92 93 95 103 104 113 114 115 143)

for id in "${projectids[@]}" ; do
	curl --request POST --header "PRIVATE-TOKEN: $PRIVATE_TOKEN" "http://10.139.6.26:7077/api/v4/projects/$id/repository/branches?branch=$branch_name&ref=$base_branch"
done

批量保护分支

此处写死了分支访问级别，可参照上文的参数进行配置

#!/usr/bin/env bash

# 访问令牌
PRIVATE_TOKEN="XXXX"
# 分支名称
branch_name=$1

# 项目ID
projectids=(47 48 50 51 52 54 55 56 58 59 60 62 63 64 65 67 68 69 70 71 74 75 89 90 91 92 93 95 103 104 113 114 115 143)

for id in "${projectids[@]}" ; do
    # 访问权限均为 Maintainer access
    curl --request POST --header "PRIVATE-TOKEN: $PRIVATE_TOKEN" "http://10.139.6.26:7077/api/v4/projects/$id/protected_branches?name=$branch_name&push_access_level=40&merge_access_level=40&unprotect_access_level=40"
done

批量取消保护分支

调用对应的删除接口即可

#!/usr/bin/env bash

# 访问令牌
PRIVATE_TOKEN="XXXX"
# 分支名称
branch_name=$1

# 项目ID
projectids=(47 48 50 51 52 54 55 56 58 59 60 62 63 64 65 67 68 69 70 71 74 75 89 90 91 92 93 95 103 104 113 114 115 143)

for id in "${projectids[@]}" ; do
    # 访问权限均为 Maintainer access
    curl --request DELETE --header "PRIVATE-TOKEN: $PRIVATE_TOKEN" "http://10.139.6.26:7077/api/v4/projects/$id/protected_branches/$branch_name"
done

批量分支封板

分支封板即设置访问级别为no one

#!/usr/bin/env bash

# 访问令牌
PRIVATE_TOKEN="XXXX"
# 分支名称
branch_name=$1

# 项目ID
projectids=(47 48 50 51 52 54 55 56 58 59 60 62 63 64 65 67 68 69 70 71 74 75 89 90 91 92 93 95 103 104 113 114 115 143)

for id in "${projectids[@]}" ; do
    # 分支封板
    curl --request POST --header "PRIVATE-TOKEN: $PRIVATE_TOKEN" "http://10.139.6.26:7077/api/v4/projects/$id/protected_branches?name=$branch_name&push_access_level=0&merge_access_level=0&unprotect_access_level=40"
done

批量删除分支

删除分支属于危险操作，操作需谨慎，因为不管是否为保护分支，都可以直接删除，而且通过api操作不会弹出确认操作

#!/usr/bin/env bash

# 访问令牌
PRIVATE_TOKEN="XXXX"
# 分支名称
branch_name=$1

# 项目ID
projectids=(47 48 50 51 52 54 55 56 58 59 60 62 63 64 65 67 68 69 70 71 74 75 89 90 91 92 93 95 103 104 113 114 115 143)

for id in "${projectids[@]}" ; do
    echo "删除项目ID：$id 的 $branch_name 分支"
    curl --request DELETE --header "PRIVATE-TOKEN: $PRIVATE_TOKEN" "http://10.139.6.26:7077/api/v4/projects/$id/repository/branches/$branch_name"
done

最后修改：2019 年 11 月 06 日

如果觉得我的文章对你有用，请随意赞赏

发表评论取消回复
使用cookie技术保留您的个人信息以便您下次快速评论，继续评论表示您已同意该条款

评论 *

私密评论

名称 *

🎲

邮箱 *

地址

GitLab Api使用

F嘉阳 • 2019 年 11 月 06 日

<h2><a id="content-使用场景" href="#content-使用场景" class="heading-permalink" aria-hidden="true" title="Permalink"></a>使用场景</h2>
<p>为了进行规范化配置管理工作，基于<code>gitlab</code>规范分支管理流程，经常需要新建分支、设置保护分支和操作分支封板等，若只有几个工程则直接在<code>gitlab</code> web界面上操作即可，一旦工程数量增多，则会消耗大量时间，故考虑可通过<code>gitlab </code>提供的web <code>api</code>编写脚本进行自动化操作</p>
<h2><a id="content-api指南" href="#content-api指南" class="heading-permalink" aria-hidden="true" title="Permalink"></a>Api指南</h2>
<p>此处摘要部分<a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/">官网</a><code>API</code>文档指南，所有<code>api</code>操作都需要在<code>gitlab</code>上申请访问令牌，该令牌应当至少包含api访问权限</p>
<p><img src="https://gitea.fjy8018.top/fjy8018/images/raw/branch/blog/img/image-20191106101754287.png" alt="image-20191106101754287" loading="lazy"  style=""></p>
<h3><a id="content-获取工程列表" href="#content-获取工程列表" class="heading-permalink" aria-hidden="true" title="Permalink"></a>获取工程列表</h3>
<p>支持多种参数过滤，非必传</p>
<blockquote>
<p>Get a list of all visible projects across GitLab for the authenticated user. When accessed without authentication, only public projects with “simple” fields are returned.</p>
<pre><code>GET /projects
</code></pre>
<table>
<thead>
<tr>
<th align="left">Attribute</th>
<th align="left">Type</th>
<th align="left">Required</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left"><code>archived</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit by archived status</td>
</tr>
<tr>
<td align="left"><code>visibility</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Limit by visibility <code>public</code>, <code>internal</code>, or <code>private</code></td>
</tr>
<tr>
<td align="left"><code>order_by</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Return projects ordered by <code>id</code>, <code>name</code>, <code>path</code>, <code>created_at</code>, <code>updated_at</code>, or <code>last_activity_at</code> fields. Default is <code>created_at</code></td>
</tr>
<tr>
<td align="left"><code>sort</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Return projects sorted in <code>asc</code> or <code>desc</code> order. Default is <code>desc</code></td>
</tr>
<tr>
<td align="left"><code>search</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Return list of projects matching the search criteria</td>
</tr>
<tr>
<td align="left"><code>simple</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Return only limited fields for each project. This is a no-op without authentication as then <em>only</em> simple fields are returned.</td>
</tr>
<tr>
<td align="left"><code>owned</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit by projects explicitly owned by the current user</td>
</tr>
<tr>
<td align="left"><code>membership</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit by projects that the current user is a member of</td>
</tr>
<tr>
<td align="left"><code>starred</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit by projects starred by the current user</td>
</tr>
<tr>
<td align="left"><code>statistics</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Include project statistics</td>
</tr>
<tr>
<td align="left"><code>with_custom_attributes</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Include <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/custom_attributes.html">custom attributes</a> in response (admins only)</td>
</tr>
<tr>
<td align="left"><code>with_issues_enabled</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit by enabled issues feature</td>
</tr>
<tr>
<td align="left"><code>with_merge_requests_enabled</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit by enabled merge requests feature</td>
</tr>
<tr>
<td align="left"><code>with_programming_language</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Limit by projects which use the given programming language</td>
</tr>
<tr>
<td align="left"><code>wiki_checksum_failed</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit projects where the wiki checksum calculation has failed (<a rel="noopener noreferrer" href="https://gitlab.com/gitlab-org/gitlab/merge_requests/6137">Introduced</a> in <a rel="noopener noreferrer" href="https://about.gitlab.com/pricing/">GitLab Premium</a> 11.2)</td>
</tr>
<tr>
<td align="left"><code>repository_checksum_failed</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Limit projects where the repository checksum calculation has failed (<a rel="noopener noreferrer" href="https://gitlab.com/gitlab-org/gitlab/merge_requests/6137">Introduced</a> in <a rel="noopener noreferrer" href="https://about.gitlab.com/pricing/">GitLab Premium</a> 11.2)</td>
</tr>
<tr>
<td align="left"><code>min_access_level</code></td>
<td align="left">integer</td>
<td align="left">no</td>
<td align="left">Limit by current user minimal <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/members.html">access level</a></td>
</tr>
</tbody>
</table>
</blockquote>
<h3><a id="content-分支操作" href="#content-分支操作" class="heading-permalink" aria-hidden="true" title="Permalink"></a>分支操作</h3>
<p><a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/branches.html">文档地址</a></p>
<h4><a id="content-创建分支" href="#content-创建分支" class="heading-permalink" aria-hidden="true" title="Permalink"></a>创建分支</h4>
<p>需要传递仓库ID、源分支名、新分支名称</p>
<blockquote>
<p>Create a new branch in the repository.</p>
<pre><code>POST /projects/:id/repository/branches
</code></pre>
<p>Parameters:</p>
<table>
<thead>
<tr>
<th align="left">Attribute</th>
<th align="left">Type</th>
<th align="left">Required</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left"><code>id</code></td>
<td align="left">integer</td>
<td align="left">yes</td>
<td align="left">ID or <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/README.html#namespaced-path-encoding">URL-encoded path of the project</a> owned by the authenticated user.</td>
</tr>
<tr>
<td align="left"><code>branch</code></td>
<td align="left">string</td>
<td align="left">yes</td>
<td align="left">Name of the branch.</td>
</tr>
<tr>
<td align="left"><code>ref</code></td>
<td align="left">string</td>
<td align="left">yes</td>
<td align="left">Branch name or commit SHA to create branch from.</td>
</tr>
</tbody>
</table>
<p>Example request:</p>
<pre><code class="language-bash">curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/5/repository/branches?branch=newbranch&ref=master
</code></pre>
</blockquote>
<h4><a id="content-保护分支" href="#content-保护分支" class="heading-permalink" aria-hidden="true" title="Permalink"></a>保护分支</h4>
<p>分支保护等级说明</p>
<blockquote>
<p><strong>Valid access levels</strong></p>
<p>The access levels are defined in the <code>ProtectedRefAccess.allowed_access_levels</code> method. Currently, these levels are recognized:</p>
<pre><code class="language-bash">0  => No access
30 => Developer access
40 => Maintainer access
60 => Admin access
</code></pre>
</blockquote>
<p>需要传递分支名称、访问级别等信息</p>
<blockquote>
<p>Protects a single repository branch or several project repository branches using a wildcard protected branch.</p>
<pre><code class="language-bash">POST /projects/:id/protected_branches
curl --request POST --header "PRIVATE-TOKEN: <your_access_token>" 'https://gitlab.example.com/api/v4/projects/5/protected_branches?name=*-stable&push_access_level=30&merge_access_level=30&unprotect_access_level=40'
</code></pre>
<table>
<thead>
<tr>
<th align="left">Attribute</th>
<th align="left">Type</th>
<th align="left">Required</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left"><code>id</code></td>
<td align="left">integer/string</td>
<td align="left">yes</td>
<td align="left">The ID or <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/README.html#namespaced-path-encoding">URL-encoded path of the project</a> owned by the authenticated user</td>
</tr>
<tr>
<td align="left"><code>name</code></td>
<td align="left">string</td>
<td align="left">yes</td>
<td align="left">The name of the branch or wildcard</td>
</tr>
<tr>
<td align="left"><code>push_access_level</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Access levels allowed to push (defaults: <code>40</code>, maintainer access level)</td>
</tr>
<tr>
<td align="left"><code>merge_access_level</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Access levels allowed to merge (defaults: <code>40</code>, maintainer access level)</td>
</tr>
<tr>
<td align="left"><code>unprotect_access_level</code></td>
<td align="left">string</td>
<td align="left">no</td>
<td align="left">Access levels allowed to unprotect (defaults: <code>40</code>, maintainer access level)</td>
</tr>
<tr>
<td align="left"><code>allowed_to_push</code></td>
<td align="left">array</td>
<td align="left">no</td>
<td align="left">Array of access levels allowed to push, with each described by a hash</td>
</tr>
<tr>
<td align="left"><code>allowed_to_merge</code></td>
<td align="left">array</td>
<td align="left">no</td>
<td align="left">Array of access levels allowed to merge, with each described by a hash</td>
</tr>
<tr>
<td align="left"><code>allowed_to_unprotect</code></td>
<td align="left">array</td>
<td align="left">no</td>
<td align="left">Array of access levels allowed to unprotect, with each described by a hash</td>
</tr>
<tr>
<td align="left"><code>code_owner_approval_required</code></td>
<td align="left">boolean</td>
<td align="left">no</td>
<td align="left">Prevent pushes to this branch if it matches an item in the <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/user/project/code_owners.html"><code>CODEOWNERS</code> file</a>. (defaults: false)</td>
</tr>
</tbody>
</table>
</blockquote>
<h4><a id="content-取消保护分支" href="#content-取消保护分支" class="heading-permalink" aria-hidden="true" title="Permalink"></a>取消保护分支</h4>
<p>需要传递仓库ID、分支名称</p>
<blockquote>
<p>Unprotects the given protected branch or wildcard protected branch.</p>
<pre><code>DELETE /projects/:id/protected_branches/:name
curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" 'https://gitlab.example.com/api/v4/projects/5/protected_branches/*-stable'
</code></pre>
<table>
<thead>
<tr>
<th align="left">Attribute</th>
<th align="left">Type</th>
<th align="left">Required</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left"><code>id</code></td>
<td align="left">integer/string</td>
<td align="left">yes</td>
<td align="left">The ID or <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/README.html#namespaced-path-encoding">URL-encoded path of the project</a> owned by the authenticated user</td>
</tr>
<tr>
<td align="left"><code>name</code></td>
<td align="left">string</td>
<td align="left">yes</td>
<td align="left">The name of the branch</td>
</tr>
</tbody>
</table>
</blockquote>
<h4><a id="content-删除分支" href="#content-删除分支" class="heading-permalink" aria-hidden="true" title="Permalink"></a>删除分支</h4>
<p>需要传递仓库ID和分支名称</p>
<blockquote>
<p>Delete a branch from the repository.</p>
<p><strong>Note:</strong> In the case of an error, an explanation message is provided.</p>
<pre><code>DELETE /projects/:id/repository/branches/:branch
</code></pre>
<p>Parameters:</p>
<table>
<thead>
<tr>
<th align="left">Attribute</th>
<th align="left">Type</th>
<th align="left">Required</th>
<th align="left">Description</th>
</tr>
</thead>
<tbody>
<tr>
<td align="left"><code>id</code></td>
<td align="left">integer/string</td>
<td align="left">yes</td>
<td align="left">ID or <a rel="noopener noreferrer" href="https://docs.gitlab.com/ee/api/README.html#namespaced-path-encoding">URL-encoded path of the project</a> owned by the authenticated user.</td>
</tr>
<tr>
<td align="left"><code>branch</code></td>
<td align="left">string</td>
<td align="left">yes</td>
<td align="left">Name of the branch.</td>
</tr>
</tbody>
</table>
<p>Example request:</p>
<pre><code class="language-bash">curl --request DELETE --header "PRIVATE-TOKEN: <your_access_token>" https://gitlab.example.com/api/v4/projects/5/repository/branches/newbranch
</code></pre>
</blockquote>
<h2><a id="content-接口测试" href="#content-接口测试" class="heading-permalink" aria-hidden="true" title="Permalink"></a>接口测试</h2>
<p>使用postman对接口进行测试</p>
<h3><a id="content-获取工程列表-1" href="#content-获取工程列表-1" class="heading-permalink" aria-hidden="true" title="Permalink"></a>获取工程列表</h3>
<p>通过该接口可以查询所有工程的ID，注意，该接口默认使用了分页</p>
<p><img src="https://gitea.fjy8018.top/fjy8018/images/raw/branch/blog/img/image-20191106102650310.png" alt="image-20191106102650310" loading="lazy"  style=""></p>
<h2><a id="content-脚本编写" href="#content-脚本编写" class="heading-permalink" aria-hidden="true" title="Permalink"></a>脚本编写</h2>
<h3><a id="content-批量创建分支" href="#content-批量创建分支" class="heading-permalink" aria-hidden="true" title="Permalink"></a>批量创建分支</h3>
<p>定义工程ID数组，对数组进行遍历，并设置基础分支变量，方便调整，此处默认写死基础分支，有需要也可以通过变量传递</p>
<pre><code class="language-bash">#!/usr/bin/env bash

# 访问令牌
PRIVATE_TOKEN="XXXX"
# 分支名称
branch_name=$1

base_branch="BasicBranch"