GitLabgitlab-org

cli

main
ply5 git calls31 ms96 KiB3 cachedprotocol v2
38 lines1.6 KiBRaw

Development process

This document describes how we make changes to the CLI. For contributing guidelines, read 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.

Who reviews the changes?

The CLI project uses the Recommend Reviewers flow. When you mark a merge request as ready, the flow assigns the minimum number of reviewers needed to satisfy each approval rule, accounting for their availability, workload, and time zone. The assignments are attributed to the flow's service account.

To pick someone else, edit the Reviewers list in the merge request sidebar.

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 can tag a release. Follow the release process.

1---
2stage: AI Clients
3group: Developer Clients
4info: To determine the technical writer assigned to the Stage/Group associated with this page, see <https://handbook.gitlab.com/handbook/marketing/product-and-technical-marketing/technical-writing/#assignments>
5---
7# Development process
9This document describes how we make changes to the CLI. For contributing guidelines,
10read [`CONTRIBUTING.md`](../CONTRIBUTING.md).
12## Who can make changes?
14**Anyone** can make changes. If you are planning larger changes that affect the
15CLI architecture or dependencies,
16[create an issue first](https://gitlab.com/gitlab-org/cli/-/issues/new?issuable_template=Feature%20Request).
18## Who reviews the changes?
20The CLI project uses the
21[Recommend Reviewers flow](https://docs.gitlab.com/user/project/merge_requests/reviews/automatic_reviewer_assignment/#recommend-reviewers-flow).
22When you mark a merge request as ready, the flow assigns the minimum number of
23reviewers needed to satisfy each approval rule, accounting for their availability,
24workload, and time zone. The assignments are attributed to the flow's service
25account.
27To pick someone else, edit the **Reviewers** list in the merge request sidebar.
29The rules for merging:
31- **Merge requests created by maintainers**: One review from a reviewer, then the
32 author maintainer may merge the merge request.
33- **Merge requests not created by maintainers**: One review from a reviewer, and one from a maintainer.
35## Who releases the changes?
37Only [project maintainers](https://gitlab.com/gitlab-org/cli/-/project_members?sort=access_level_desc)
38can tag a release. Follow the [release process](release_process.md).
Diagnostics5 git calls · 31 ms
CallStatusSizeTime031 ms
discover200185 B4 ms
git.upload-pack discover
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=185
git.server.agent=git/2.56.g1891de4-Linux
git.server.object_format=sha1
git.server.caps=agent ls-refs fetch server-option object-format
git.server.fetch=shallow wait-for-done filter
git.protocol.version=2
git.pkt.frames=9
git.pkt.data=7
git.pkt.flush=2
git.pkt.delim=0
git.pkt.bytes=185
git.pkt.payload.max=35
ls-refs20058 KiB3 ms
git.upload-pack ls-refs
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=ls-refs
git.upstream.dur_ms=3
git.response.bytes=59849
git.response.cache=UPDATING
git.response.duration_ms=3
git.protocol.version=2
git.pkt.frames=731
git.pkt.data=730
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=59849
git.pkt.payload.max=143
git.ls_refs.count=730
git.ls_refs.head=refs/heads/main
fetchcombine:blob:none+tree:2 · deepen 12004.2 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=2
git.response.bytes=4273
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=combine:blob:none+tree:2
git.fetch.wants=0dd7574dce9e385c5c30540e6c15657adc6bdce9
git.fetch.haves.count=0
git.fetch.deepen=1
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=7
git.pkt.data=5
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=4273
git.pkt.payload.max=4173
git.sideband.band1.bytes=4173
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=11
git.pack.bytes=4173
git.fetch.wide.objects=11
git.fetch.wide.extra_bytes=3930
git.fetch.wide.blobs=0
fetchtree:0 · deepen 1020032 KiB · hit2 ms
git.upload-pack fetch
http.response.status_code=200
git.upstream.cf_ray=-
git.upstream.phase=fetch
git.upstream.dur_ms=25
git.response.bytes=32926
git.response.cache=HIT
git.response.duration_ms=2
git.fetch.filter=tree:0
git.fetch.wants=0dd7574dce9e385c5c30540e6c15657adc6bdce9
git.fetch.haves.count=0
git.fetch.deepen=10
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=22
git.pkt.data=20
git.pkt.flush=1
git.pkt.delim=1
git.pkt.bytes=32926
git.pkt.payload.max=32046
git.sideband.band1.bytes=32046
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0
git.pack.objects=80
git.pack.bytes=32046
git.pack.ofs_delta=36
git.pack.ref_delta=0
git.pack.chain.max=2
git.pack.trailer=cb0bad5d7ffc514895d8b21c4dd470327f90bc91
git.pack.full=44
Open pack map
fetch200879 B · hit25 ms
git.upload-pack fetch
http.response.status_code=200
git.response.bytes=879
git.response.cache=HIT
git.response.duration_ms=25
git.fetch.wants=142f81f2813988c181fbdffd3cf2bc0c4016350c
git.fetch.haves.count=0
git.fetch.deepen=0
git.fetch.thin_pack=false
git.fetch.ofs_delta=true
git.protocol.version=2
git.pkt.frames=4
git.pkt.data=3
git.pkt.flush=1
git.pkt.delim=0
git.pkt.bytes=879
git.pkt.payload.max=852
git.sideband.band1.bytes=852
git.sideband.band2.bytes=0
git.sideband.band3.bytes=0

Each row is one HTTP round trip ply made to the git server for this page, on one timeline. discover asks what the server speaks, ls-refs lists branch tips, fetch brings objects by id. A hit was served by Workers Cache. Tap a row for its wire details.

Remote
https://gitlab.com/gitlab-org/cli
Ref
refs/heads/main
Commit
0dd7574dce9e385c5c30540e6c15657adc6bdce9
cf-ray
a5e1131b08e55e37
Request
00576a16…
Protocol
v2 · sha1
Agent
git/2.56.g1891de4-Linux
Filter
advertised
Fetch
shallow wait-for-done filter
Capabilities
agent ls-refs fetch server-option object-format