From 8dedf9d0be823d99481505c52f3e101a54dc8a85 Mon Sep 17 00:00:00 2001 From: Vincent Ambo Date: Wed, 24 Jun 2020 02:32:35 +0100 Subject: chore: Update 'master -> canon' in various places Change-Id: I901c023f707a0223af673c217c65434e26e2ab1f Reviewed-on: https://cl.tvl.fyi/c/depot/+/568 Reviewed-by: lukegb --- docs/REVIEWS.md | 6 +++--- 1 file changed, 3 insertions(+), 3 deletions(-) (limited to 'docs') diff --git a/docs/REVIEWS.md b/docs/REVIEWS.md index 5be81acbef..3f0036456b 100644 --- a/docs/REVIEWS.md +++ b/docs/REVIEWS.md @@ -49,13 +49,13 @@ and all development happens at `HEAD`. Every time you create a new commit the change hook will insert a unique `Change-Id` tag into the commit message. Once you are satisfied with the state of your commit and want to submit it for review, you push it to a git ref called -`refs/for/master`. This designates the commits as changelists (CLs) targeted for -the `master` branch. +`refs/for/canon`. This designates the commits as changelists (CLs) targeted for +the `canon` branch. ``` Example: git commit -m 'docs(REVIEWS): Fixed all the errors in the reviews docs' -git push origin HEAD:refs/for/master +git push origin HEAD:refs/for/canon ``` TIP: Every individual commit will become a separate change. We do not merge -- cgit 1.4.1