From 390bf522c865560e64abc42f36ec59a1509d4ee4 Mon Sep 17 00:00:00 2001 From: Justin SB Date: Sun, 20 Feb 2022 13:27:02 -0500 Subject: [PATCH] docs for release process shouldn't assume remotes `gh pr create` will prompt to push upstream, and our docs assumed that origin was the user's fork, but that is often not the case. --- docs/contributing/release-process.md | 4 ---- 1 file changed, 4 deletions(-) diff --git a/docs/contributing/release-process.md b/docs/contributing/release-process.md index 77b7d0a961..ef17ee7f29 100644 --- a/docs/contributing/release-process.md +++ b/docs/contributing/release-process.md @@ -73,7 +73,6 @@ git add . && git commit -m "Release ${VERSION}" This is the "release commit". Push and create a PR. ``` -git push -u origin release_${VERSION} gh pr create -f ``` @@ -124,7 +123,6 @@ Review then send a PR with the release notes: ``` git add -p docs/releases/${DOC}-NOTES.md git commit -m "Release notes for ${VERSION}" -git push -u origin relnotes_${VERSION} gh pr create -f ``` @@ -156,7 +154,6 @@ Currently we send the image and non-image artifact promotion PRs separately. cd ${GOPATH}/src/k8s.io/k8s.io git add -p k8s.gcr.io/images/k8s-staging-kops/images.yaml git commit -m "Promote kOps $VERSION images" -git push -u origin kops_images_${VERSION} gh pr create -f ``` @@ -181,7 +178,6 @@ Verify, then send a PR: ``` git add artifacts/manifests/k8s-staging-kops/${VERSION}.yaml git commit -m "Promote kOps $VERSION binary artifacts" -git push -u origin kops_artifacts_${VERSION} gh pr create -f ```