1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
16
17
18
19
20
21
22
23
24
25
26
27
28
29
30
31
32
33
|
---
stage: Create
group: Code Review
info: To determine the technical writer assigned to the Stage/Group associated with this page, see https://about.gitlab.com/handbook/product/ux/technical-writing/#assignments
---
# Development process
This document describes how we make changes to the CLI. For contributing guidelines,
read [`CONTRIBUTING.md`](../CONTRIBUTING.md).
## Who can make changes?
**Anyone** can make changes. If you are planning larger changes that affect the
CLI architecture or dependencies,
[create an issue first](https://gitlab.com/gitlab-org/cli/-/issues/new?issuable_template=Feature%20Request).
## Who reviews the changes?
The CLI project has [reviewer roulette](https://gitlab.com/gitlab-org/cli/-/merge_requests/1093).
Each merge request receives a comment including a suggested reviewer and maintainer.
Assign the reviewer first.
The rules for merging:
- **Merge requests created by maintainers**: One review from a reviewer, then the
author maintainer may merge the merge request.
- **Merge requests not created by maintainers**: One review from a reviewer, and one from a maintainer.
## Who releases the changes?
Only [project maintainers](https://gitlab.com/gitlab-org/cli/-/project_members?sort=access_level_desc)
can tag a release. Follow the [release process](release_process.md).
|
