From 4f5e582e964b53f956e4567b98d64ca2012327f8 Mon Sep 17 00:00:00 2001
From: Richard Levasseur <rlevasseur@google.com>
Date: Wed, 27 Aug 2025 22:37:48 -0700
Subject: [PATCH] docs: tell how to push one tag; that rc start with n=0

---
 RELEASING.md | 9 +++++----
 1 file changed, 5 insertions(+), 4 deletions(-)

diff --git a/RELEASING.md b/RELEASING.md
index a99b7d8d00..e72ff619ba 100644
--- a/RELEASING.md
+++ b/RELEASING.md
@@ -28,9 +28,10 @@ The next step is to create tags to trigger release workflow, **however**
 we start by using release candidate tags (`X.Y.Z-rcN`) before tagging the
 final release (`X.Y.Z`).
 
-1. Create release candidate tag and push. Increment `N` for each rc.
+1. Create release candidate tag and push. The first RC uses `N=0`. Increment
+   `N` for each RC.
    ```
-   git tag X.Y.0-rcN upstream/release/X.Y && git push upstream --tags
+   git tag X.Y.0-rcN upstream/release/X.Y && git push upstream tag X.Y.0-rcN
    ```
 2. Announce the RC release: see [Announcing Releases]
 3. Wait a week for feedback.
@@ -38,8 +39,8 @@ final release (`X.Y.Z`).
      release branch.
    * Repeat the RC tagging step, incrementing `N`.
 4. Finally, tag the final release tag:
-   ```
-   git tag X.Y.0 upstream/release/X.Y && git push upstream --tags
+   ```shell
+   git tag X.Y.0 upstream/release/X.Y && git push upstream tag X.Y.0
    ```
 
 Release automation will create a GitHub release and BCR pull request.