Create a merge request that adds cli: reviewer under projects: in your team member entry in www-gitlab-com (example). If you already have a projects: key, add the line to it:
Community contributions pick reviewers from the reviewer roulette, which is rebuilt from the team database. You start receiving them after the next roulette build.
Review merge requests
Before you review, it helps to have a passing GitLab Duo Code Review. This applies to community contributions and all other merge requests. GitLab Duo Code Review checks changes against the project conventions in .gitlab/duo/mr-review-instructions.yaml.
For risky or complex changes, ask an agent to build glab from main and from the merge request branch. Have it run the changed commands with both binaries and compare the results. This finds defects that a review of the diff can miss.
The CLI follows the handbook's accelerated maintainer onboarding for smaller projects. Apply when you feel confident in the codebase, for example after you've authored and reviewed a few merge requests. If you have strong Go experience, you may need fewer. Ask in #f_cli if you're unsure.
Create a merge request that changes your team member entry to cli: maintainer (example). Link your onboarding issue, assign it to your manager, and ask a CLI maintainer to approve. Once it merges, you're also assigned dependency update merge requests from gitlab-dependency-update-bot (Renovate).
Domain teams that own a subtree of this repository do not need the Maintainer role. Approval, merging, and administration are separate controls. See Path ownership and merge access.
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>
171. Create a merge request that adds `cli: reviewer` under `projects:` in your
18 [team member entry](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/master/doc/team_database.md)
19 in `www-gitlab-com` ([example](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/3284a59d69e2b2ae9bb1fb8bc03b6be2d29aa6cb/data/team_members/person/d/dbickford.yml#L13-14)). If you already have a `projects:` key, add
551. Create a merge request that changes your team member entry to
56 `cli: maintainer` ([example](https://gitlab.com/gitlab-com/www-gitlab-com/-/blob/3284a59d69e2b2ae9bb1fb8bc03b6be2d29aa6cb/data/team_members/person/j/jay_mccure.yml#L20-23)). Link your onboarding issue, assign it to
57 your manager, and ask a CLI maintainer to approve. Once it merges, you're also
58 assigned dependency update merge requests from `gitlab-dependency-update-bot` (Renovate).
99- Code changes follow the project conventions in [`.gitlab/duo/mr-review-instructions.yaml`](../.gitlab/duo/mr-review-instructions.yaml). GitLab Duo Code Review can check this for you.
100- Required approvals from appropriate code owners or domain teams are satisfied (see [Path ownership and merge access](path_ownership.md)).
101- The merge request title follows [Conventional Commits](https://www.conventionalcommits.org/). Squash is on by default, so the title becomes the commit message on `main`.
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.