Fix GitHub Actions Authentication Issue #72
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Feedback (click)
I created this PR to fix the failing GitHub Actions.## Description
This PR addresses the issue with the failing GitHub Actions due to bad credentials. The problem was identified to be with the
dessant/lock-threads@v4
action in the.github/workflows/lock-threads.yml
workflow file.The issue was resolved by ensuring that the correct secrets are being used for authentication. The secrets used by the
cla.yml
andrelease.yml
workflows, which aresecrets.BOT_GITHUB_TOKEN
andsecrets.REDBOT_GITHUB_TOKEN
respectively, were used to authenticate thedessant/lock-threads@v4
action.Summary of Changes
.github/workflows/lock-threads.yml
workflow file to use the correct secrets for authentication.env
subsection in the section that uses thedessant/lock-threads@v4
action to use thesecrets.BOT_GITHUB_TOKEN
secret for authentication.env
subsection was already present, ensured that it uses the correct secret for authentication.