Move remote push of branch from step 1 to step 5

Author: qdm12

libevm/tooling/release/README.md

@@ -10,7 +10,6 @@ In the following, we create a release candidate version `v1.13.14-0.2.0.rc.4`.
     git checkout -b release/v1.13.14-0.2.0.rc.4
     git push -u origin release/v1.13.14-0.2.0.rc.4
     git checkout -b myusername/release/v1.13.14-0.2.0.rc.4
-    git push -u origin myusername/release/v1.13.14-0.2.0.rc.4
     ```
 
     The `myusername/release/v1.13.14-0.2.0.rc.4` branch will be used to add "release modifications" and will target the branch `release/v1.13.14-0.2.0.rc.4` in a pull request.
@@ -21,7 +20,7 @@ In the following, we create a release candidate version `v1.13.14-0.2.0.rc.4`.
     - If planning a release candidate: set `libEVMReleaseCandidate` to the correct number; in this case `4`
     - If needed: change the `LibEVMVersionMajor`, `LibEVMVersionMinor` and `LibEVMVersionPatch` numbers
 1. Commit your modifications to [params/version.libevm.go](/params/version.libevm.go) with a commit title `chore: release v1.13.14-0.2.0.rc.4`.
-1. Push your modified branch to the remote `git push`
+1. Push your modified branch to the remote `git push -u origin myusername/release/v1.13.14-0.2.0.rc.4`
 1. Open a pull request from your modified branch `myusername/release/v1.13.14-0.2.0.rc.4` and targeting `release/v1.13.14-0.2.0.rc.4`, for example with `https://github.com/ava-labs/libevm/compare/release/v1.13.14-0.2.0.rc.4...myusername/release/v1.13.14-0.2.0.rc.4?expand=1`. Set the tile to "chore: release `v1.13.14-0.2.0.rc.4`"
 1. Wait for all the checks to pass on the pull request
 1. Fast forward merge your branch in the release branch: