From f1b00de693414891d96b4b1ba57e2aeb90a75529 Mon Sep 17 00:00:00 2001
From: Gauthier Petetin <gauthierpetetin@hotmail.com>
Date: Tue, 22 Aug 2023 07:49:36 -0300
Subject: [PATCH] fix(action): octokit not supported on MetaMask repos (#20544)

* fix(action): octokit not supported on MetaMask repos

The github action was constantly failing with the following error: octokit/request-action@v2.x is not allowed to be used in MetaMask/metamask-extension

* fix(action): shellcheck was failing

Shellcheck was failing in the CI. Had to craft the payload of the curl before doing the curl to fix this.
---
 .github/workflows/create-bug-report.yml | 40 +++++++++----------------
 1 file changed, 14 insertions(+), 26 deletions(-)

diff --git a/.github/workflows/create-bug-report.yml b/.github/workflows/create-bug-report.yml
index f46296bea..33535e491 100644
--- a/.github/workflows/create-bug-report.yml
+++ b/.github/workflows/create-bug-report.yml
@@ -19,29 +19,17 @@ jobs:
 
       - name: Create bug report issue on planning repo
         if: env.version
-        uses: octokit/request-action@v2.x
-        with:
-          route: POST /repos/MetaMask/MetaMask-planning/issues
-          owner: MetaMask
-          title: v${{ env.version }} Bug Report
-          body: |
-            This bug report was automatically created by a GitHub action upon the creation of release branch `Version-v${{ env.version }}` (release cut).
-
-
-            **Expected actions for release engineers:**
-
-            1. Convert this issue into a Zenhub epic and link all bugs identified during the release regression testing phase to this epic.
-
-            2. After completing the first regression run, move this epic to "Regression Completed" on the [Extension Release Regression board](https://app.zenhub.com/workspaces/extension-release-regression-6478c62d937eaa15e95c33c5/board?filterLogic=any&labels=release-${{ env.version }},release-task).
-
-
-            Note that once the release is prepared for store submission, meaning the `Version-v${{ env.version }}` branch merges into `master`, another GitHub action will automatically close this epic.
-
-          labels: |
-            [
-              "type-bug",
-              "regression-RC",
-              "release-${{ env.version }}"
-            ]
-        env:
-          GITHUB_TOKEN: ${{ secrets.BUG_REPORT_TOKEN }}
+        run: |
+          payload=$(cat <<EOF
+          {
+            "title": "v${{ env.version }} Bug Report",
+            "body": "This bug report was automatically created by a GitHub action upon the creation of release branch \`Version-v${{ env.version }}\` (release cut).\n\n**Expected actions for release engineers:**\n\n1. Convert this issue into a Zenhub epic and link all bugs identified during the release regression testing phase to this epic.\n\n2. After completing the first regression run, move this epic to \"Regression Completed\" on the [Extension Release Regression board](https://app.zenhub.com/workspaces/extension-release-regression-6478c62d937eaa15e95c33c5/board?filterLogic=any&labels=release-${{ env.version }},release-task).\n\nNote that once the release is prepared for store submission, meaning the \`Version-v${{ env.version }}\` branch merges into \`master\`, another GitHub action will automatically close this epic.",
+            "labels": ["type-bug", "regression-RC", "release-${{ env.version }}"]
+          }
+          EOF
+          )
+          curl -X POST \
+            -H "Authorization: token ${{ secrets.BUG_REPORT_TOKEN }}" \
+            -H "Accept: application/vnd.github.v3+json" \
+            https://api.github.com/repos/MetaMask/MetaMask-planning/issues \
+            -d "$payload"