From 67888a17d628194b935f22b56e20811034ab5c44 Mon Sep 17 00:00:00 2001 From: Rodrigo Tavares Date: Wed, 17 Jul 2024 18:52:58 +0200 Subject: [PATCH] Clarify pull request usage in README Signed-off-by: Rodrigo Tavares Update README.md Thanks @dhaiducek Co-authored-by: Dale Haiducek <19750917+dhaiducek@users.noreply.github.com> Signed-off-by: Rodrigo Tavares (cherry picked from commit 2b0640622ba918f14c69010a481989e87405fa0d) --- README.md | 10 +++++----- 1 file changed, 5 insertions(+), 5 deletions(-) diff --git a/README.md b/README.md index c5059e0b..9d612778 100644 --- a/README.md +++ b/README.md @@ -14,11 +14,11 @@ folders: ## Using GitOps to deploy policies to a cluster -Fork this repository and use the forked version as the target to run the sync against. This is to -avoid unintended changes to be applied to your cluster automatically. To get latest policies from -the `policy-collection` repository, you can pull the latest changes from `policy-collection` to your -own repository through a pull request. Any further changes to your repository are automatically be -applied to your cluster. +Fork this repository and use the forked version as the target to run the sync. This avoids +unintended changes to your cluster. To get the latest policies from the `policy-collection` +repository, pull the latest changes from `policy-collection` and then create a pull request to merge +these changes into your forked repository. Any further changes to your repository will be applied to +your cluster automatically. Make sure you have [kubectl](https://kubernetes.io/docs/tasks/tools/install-kubectl/) installed and that you are logged into your hub cluster in terminal.