From f9d658d3b453c4ffb5dcbd756e1298c9e319b4ab Mon Sep 17 00:00:00 2001
From: Muhammad Safwan Karim <66724151+msafwankarim@users.noreply.github.com>
Date: Mon, 25 Aug 2025 18:50:27 +0500
Subject: [PATCH] Clarify PR process for Helm chart version updates (#1003)

Updated instructions for creating a PR to include a specific label for Helm chart version updates.
---
 README.md | 2 +-
 1 file changed, 1 insertion(+), 1 deletion(-)

diff --git a/README.md b/README.md
index 3e887e4a..c70a12ae 100644
--- a/README.md
+++ b/README.md
@@ -420,7 +420,7 @@ To make a GitHub release:
 1. Code owners run a dispatch mode workflow to automatically generate version and manifests on the release branch
 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 a PR to update the Helm chart version, example: [PR-846](https://github.com/stakater/Reloader/pull/846)
+1. Code owners create a PR with `release/helm-chart` label to update the Helm chart version, 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.