docs(release): add branch information so the correct commit is tagged
@@ -81,7 +81,7 @@ The following changes should be present:
- `website/content/en/docs/upgrading-sdk-version/v1.3.0.md`: commit changes (created by changelog generation).
- `website/config.toml`: commit changes (modified by release script).
-Commit these changes and push:
+Commit these changes and push to your remote (assuming your remote is named `origin`):
```sh
git add --all
@@ -98,9 +98,14 @@ if you have admin access to the operator-sdk repo, or ask an administrator to do
Unlock the branch by changing the number of required approving reviewers in the `master` branch rule back to 1.
-### 4. Create and push a release tag
+### 4. Create and push a release tag on `master`
+
+Refresh your local `master` branch, tag the release PR commit, and push to the main operator-sdk repo
+(assumes the remote's name is `upstream`):
```sh
+git checkout master
+git pull
make tag
git push upstream refs/tags/$RELEASE_VERSION
```
@@ -112,7 +117,7 @@ Run the following commands to do so:
```sh
git checkout latest
-git reset --hard tags/$RELEASE_VERSION
+git reset --hard refs/tags/$RELEASE_VERSION
git push -f upstream latest
```
@@ -120,7 +125,7 @@ Similarly, to update the release branch, run:
```sh
git checkout v1.3.x
-git reset --hard tags/$RELEASE_VERSION
+git reset --hard refs/tags/$RELEASE_VERSION
git push -f upstream v1.3.x
```
