kubernetes
/
kops
mirror of https://github.com/kubernetes/kops.git
1
0
Fork 0
Code Issues Packages Projects Releases Wiki Activity

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.
This commit is contained in:
Justin SB 2022-02-20 13:27:02 -05:00
parent d400da0d4c
commit 390bf522c8
1 changed files with 0 additions and 4 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

4
docs/contributing/release-process.md
View File

@ -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
```