From a23630a7ac75ce9fe4b30855b3495b90289f5186 Mon Sep 17 00:00:00 2001
From: Patrick Lee Scott <pat@patscott.io>
Date: Fri, 31 Jan 2025 11:27:56 -0600
Subject: [PATCH] feat: make PR with changes to deal with branch protection
 rules

fix: from new branch

fix: syntax

fix: syntax

fix: pr permissions

fix: pr details
---
 .github/workflows/publish-helm.yaml | 37 ++++++++++++++++++++++++++---
 1 file changed, 34 insertions(+), 3 deletions(-)

diff --git a/.github/workflows/publish-helm.yaml b/.github/workflows/publish-helm.yaml
index dc0780f14..d18e39809 100644
--- a/.github/workflows/publish-helm.yaml
+++ b/.github/workflows/publish-helm.yaml
@@ -9,6 +9,7 @@ jobs:
 
     permissions:
       contents: write
+      pull-requests: write
 
     runs-on: ubuntu-latest
     steps:
@@ -65,7 +66,37 @@ jobs:
             git config --local user.email "github-actions[bot]@users.noreply.github.com"
             git config --local user.name "github-actions[bot]"
             git add -A
-            git commit -m "update helm chart repository index.yaml"
-
-            git push origin gh-pages
+            git commit -m "update helm chart repository index"
           fi
+
+      - name: Create Pull Request
+        uses: peter-evans/create-pull-request@v7
+        with:
+          branch: feat/update-helm-repo-index-${{ github.sha }}
+          base: gh-pages
+          title: Update Helm Chart Repository Index
+          body: |
+            <!-- 
+            Are you using Knative? If you do, we would love to know!
+            https://github.com/knative/community/issues/new?template=ADOPTERS.yaml&title=%5BADOPTERS%5D%3A+%24%7BCOMPANY+NAME+HERE%7D
+            -->
+
+            <!--
+            Request Prow to automatically lint any go code in this PR:
+
+            /lint
+            -->
+
+            ## Proposed Changes
+
+            * Update Helm Chart Repository Index - generated by the publish-helm.yaml workflow
+
+            **Release Note**
+
+            <!-- Enter your extended release note in the below block. If the PR requires
+            additional action from users switching to the new release, include the string
+            "action required". If no release note is required, write "NONE". -->
+
+            ```release-note
+            NONE
+            ```