Skip to content

Commit

Permalink
release-process: explain that you need to push the branch
Browse files Browse the repository at this point in the history
Signed-off-by: Maël Valais <mael@vls.dev>
  • Loading branch information
maelvls committed Sep 1, 2023
1 parent ddac0eb commit b263e32
Showing 1 changed file with 8 additions and 0 deletions.
8 changes: 8 additions & 0 deletions content/docs/contributing/release-process.md
Original file line number Diff line number Diff line change
Expand Up @@ -450,6 +450,14 @@ page if a step is missing or if it is outdated.
[how-are-versions-of-a-sub-module-managed]:
https://stackoverflow.com/questions/60601011/how-are-versions-of-a-sub-module-managed/60601402#60601402
Then, push the branch to your fork of cert-manager. For example:
```bash
# Must be run from the cert-manager repo folder.
gh repo fork --remote-name fork
git push -u fork "update-cmd/ctl/$RELEASE_VERSION"
```
Then, open a PR to merge that change and go back to the release branch with
the following commands:
Expand Down

0 comments on commit b263e32

Please sign in to comment.