release docs: bin/mkrelease (now) pushes tags

That makes the warning in the docs confusing, since they'll be pushed as part of the process.
zRedShift · Nov 6, 2020 · 4959977 · 4959977
1 parent a647173
commit 4959977
Showing 1 changed file with 3 additions and 6 deletions.
diff --git a/.github/ISSUE_TEMPLATE/release.md b/.github/ISSUE_TEMPLATE/release.md
@@ -47,20 +47,17 @@ production readiness.
   ```shell
   tag=v<VERSION>-rc<N>
   bin/mkrelease -b rel-$tag $tag
-  git push origin $tag
   ```
 
-- [ ] *After* you have pushed that tag, on `main`, do the same thing for the
-  dev version, without creating a tag:
+- [ ] Incorporate this tag into `main`'s history by preparing dev on top of it.
+
+  Without switching to `main`, perform:
 
   ```shell
   next=v<NEXT_VERSION>-dev
   bin/mkrelease --no-tag -b prepare-$next $next
   ```
 
-  This must be done after the tag has been pushed, or Git will delete the tag
-  that isn't on the server.
-
   - [ ] Open a PR with this change, and land it.
 
 ### Review Release Notes