m
/
metamask-extension
mirror of https://github.com/kremalicious/metamask-extension.git
1
0
Fork 0
Code

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.
This commit is contained in:
Gauthier Petetin 2023-08-22 07:49:36 -03:00 committed by GitHub
parent 37209a7d2e
commit f1b00de693
No known key found for this signature in database
GPG Key ID: 4AEE18F83AFDEB23
1 changed files with 14 additions and 26 deletions
Show Stats Download Patch File Download Diff File Expand all files Collapse all files

40
.github/workflows/create-bug-report.yml vendored
View File

@ -19,29 +19,17 @@ jobs:
- name: Create bug report issue on planning repo - name: Create bug report issue on planning repo
if: env.version if: env.version
uses: octokit/request-action@v2.x run: |
with: payload=$(cat <<EOF
route: POST /repos/MetaMask/MetaMask-planning/issues {
owner: MetaMask "title": "v${{ env.version }} Bug Report",
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.",
body: | "labels": ["type-bug", "regression-RC", "release-${{ env.version }}"]
This bug report was automatically created by a GitHub action upon the creation of release branch `Version-v${{ env.version }}` (release cut). }
EOF
)
**Expected actions for release engineers:** curl -X POST \
-H "Authorization: token ${{ secrets.BUG_REPORT_TOKEN }}" \
1. Convert this issue into a Zenhub epic and link all bugs identified during the release regression testing phase to this epic. -H "Accept: application/vnd.github.v3+json" \
https://api.github.com/repos/MetaMask/MetaMask-planning/issues \
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). -d "$payload"
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 }}