Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

minor typo fix on version release guide #144

Merged
merged 2 commits into from
Oct 10, 2023
Merged

minor typo fix on version release guide #144

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
5e4f846
minor typo fix on verison release guide
ssyno Oct 10, 2023
3c422f3
small addition to explanation
ssyno Oct 10, 2023
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
4 changes: 2 additions & 2 deletions content/docs/dev-and-releng/releases/how-to-release-a-project/_index.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -36,14 +36,14 @@ Once workflows are ready, it is time to create release branch. The name
of the branch is important and it must follow this convention:

```
${BASE}#release#v${VERSION}
${BASE}#release#${VERSION}
```

Where:

- `BASE` - is the name of the base branch for release PR. Usually it is
`master` or `main`.
- `VERSION` - either `major`, `minor`, `patch` or a specific version that is going to be created for the release.
- `VERSION` - either `major`, `minor`, `patch` or a specific version `v1.2.3` that is going to be created for the release.

Example:

Expand Down