Currently when filing a PR ready to be reviewed or approved, the GitHub CI/CD action "Add issue to project" fires and fails, every time. It sends an email to the developer filing the PR that "Add Project to New Issue have failed." When you click the "View workflow run" in that email, it takes you the GitHub Actions CI/CD here in this repository, and if you click the "Add issue to project" GitHub action button, it runs it and fails, yet again, with Error: Bad credentials. See attached screenshots of this.
Expected behavior:
There should be a proper secret key in a .env file that this GitHub action pulls from, so that this Action does not fail and we can add new Issues to a Project without getting this error/fail & notifying email.
Actual Behavior:
The GitHub Action fails, apparently while trying to pull a secret key authenticate the action, and sends an error email to the developer and the CI/CD for this never completes.
Screenshots:
To Reproduce:
Steps to reproduce the behavior:
See above description & screenshots
Desktop (please complete the following information):
@leekahung has suggested that the GitHub actions are trying to authenticate this step and get a secret key from a .env file somewhere, and the key is either the general key for CodeForPDX and not for PASS's repository GItHub Actions CI/CD, or is not there at all.
We should either generate a secret key for these actions that works and makes this GitHub Action work, or, it was suggested by others in the Dev Meeting on 26-March-2024 that we should just get rid of this action and tag issues using the GitHub template instead.
Describe the bug:
Currently when filing a PR ready to be reviewed or approved, the GitHub CI/CD action "Add issue to project" fires and fails, every time. It sends an email to the developer filing the PR that "Add Project to New Issue have failed." When you click the "View workflow run" in that email, it takes you the GitHub Actions CI/CD here in this repository, and if you click the "Add issue to project" GitHub action button, it runs it and fails, yet again, with
Error: Bad credentials.See attached screenshots of this.Expected behavior:
There should be a proper secret key in a
.envfile that this GitHub action pulls from, so that this Action does not fail and we can add new Issues to a Project without getting this error/fail & notifying email.Actual Behavior:
The GitHub Action fails, apparently while trying to pull a secret key authenticate the action, and sends an error email to the developer and the CI/CD for this never completes.
Screenshots:
To Reproduce:
Steps to reproduce the behavior:
See above description & screenshots
Desktop (please complete the following information):
Possible Fix:
@leekahung has suggested that the GitHub actions are trying to authenticate this step and get a secret key from a
.envfile somewhere, and the key is either the general key for CodeForPDX and not for PASS's repository GItHub Actions CI/CD, or is not there at all.We should either generate a secret key for these actions that works and makes this GitHub Action work, or, it was suggested by others in the Dev Meeting on 26-March-2024 that we should just get rid of this action and tag issues using the GitHub template instead.
Additional context:
Add any other context about the problem here.