blob: ff7afe1feb3cca9fa59fcf2c1ab768dc9eac6ad6 (
plain)
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
|
---
breadcrumbs:
- - /chromium-os
- Chromium OS
- - /chromium-os/how-tos-and-troubleshooting
- How Tos and Troubleshooting
page_name: create-a-cl
title: Create a CL
---
For a more thorough introduction, see the [appropriate section of the Developer
Guide](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/developer_guide.md#making-changes-to-packages-whose-source-code-is-checked-into-chromium-os-git-repositories).
Here's the basic flow when creating/uploading a CL for review:
1. Navigate to the project you want to create a CL for, I'll use
src/scripts as an example: cd ~/trunk/src/scripts
2. Start a new branch that tracks the remote master branch: repo start
<name of branch to create> .
3. Make the changes you want to upload, and then commit them, following
the [commit message
format](https://chromium.googlesource.com/chromiumos/docs/+/HEAD/contributing.md#Commit-messages).
4. Upload your CL by typing repo upload . --cbr
5. You'll get given a URL to your CL on Gerrit where it'll be reviewed.
Add some reviewers and wait for them to check your change.
6. Once you've been given +2 for your change, mark it verified assuming
you've verified it works and commit ready.
7. Wait for the commit queue to pick your change up. If it passes the
commit queue, it'll be merged. If it fails, a comment will be posted
on the review and you'll get an email telling you as such.
8. Congrats! You've contributed your change!
|
