From 32046ebfe0d7213646af53f5ea6b615f9f55a0cf Mon Sep 17 00:00:00 2001 From: Safwan Date: Wed, 5 Nov 2025 14:04:49 +0500 Subject: [PATCH] Fixed spelling --- README.md | 2 +- 1 file changed, 1 insertion(+), 1 deletion(-) diff --git a/README.md b/README.md index 32901856..ea1c77c9 100644 --- a/README.md +++ b/README.md @@ -439,7 +439,7 @@ To make a GitHub release: - Set the `TARGET_VERSION` to release version without 'v' i.e. `X.Y.Z` 1. A PR is created to bump the image version on the release branch, example: [PR-798](https://github.com/stakater/Reloader/pull/798) 1. Code owners create a GitHub release with tag `vX.Y.Z` and target branch `release-vX.Y.Z`, which triggers creation of images -1. Code owners create another branch from master and bump the helm chart version as well as reloader image version. +1. Code owners create another branch from `master` and bump the helm chart version as well as Reloader image version. - Code owners create a PR with `release/helm-chart` label, example: [PR-846](https://github.com/stakater/Reloader/pull/846) _Repository git tagging_: Push to the main branch will create a merge-image and merge-tag named `merge-${{ github.event.number }}`, for example `merge-800` when pull request number 800 is merged.