[GitHub] [beam] TheNeuralBit commented on a change in pull request #12015: Clarify release guide for publishing release notes to GitHub

[GitBox <gi...@apache.org>]

TheNeuralBit commented on a change in pull request #12015:
URL: https://github.com/apache/beam/pull/12015#discussion_r440464906



##########
File path: website/www/site/content/en/contribute/release-guide.md
##########
@@ -1126,21 +1126,28 @@ Verify that:
 * Images with *latest* tag are pointing to current release by confirming 
   1. Digest of the image with *latest* tag is the same as the one with {RELEASE} tag.
 
+### Merge website pull request
+
+Merge the website pull request to [list the release](/get-started/downloads/), publish the [Python API reference manual](https://beam.apache.org/releases/pydoc/), the [Java API reference manual](https://beam.apache.org/releases/javadoc/) and Blogpost created earlier.
+
 ### Git tag
 
 Create and push a new signed tag for the released version by copying the tag for the final release candidate, as follows:
 
-    VERSION_TAG="v${RELEASE}"
-    git tag -s "$VERSION_TAG" "$RC_TAG"
-    git push upstream "$VERSION_TAG"
+```
+VERSION_TAG="v${RELEASE}"
+git tag -s "$VERSION_TAG" "$RC_TAG"
+git push origin "$VERSION_TAG"

Review comment:
       Yeah, I just figured that `origin` is closer to a standard than `upstream`. That's a great point that we can just use the full URL though




----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.

For queries about this service, please contact Infrastructure at:
users@infra.apache.org