Fix Bad Credentials Error in GitHub Actions #50
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 of the failing GitHub Actions due to bad credentials. The error was thrown by the
dessant/lock-threads@v4
action. The issue was due to incorrect or missing credentials being passed to the action.Summary of Changes
.github/workflows/lock-threads.yml
file to ensure the correct GitHub token and personal access token (if required) are being passed to thedessant/lock-threads@v4
action.env
section under thedessant/lock-threads@v4
action to ensure theGITHUB_TOKEN
is correctly set to${{ secrets.GITHUB_TOKEN }}
.dessant/lock-threads@v4
action, ensured it's correctly set in theenv
section. The field name might vary, but it should be set in a similar way to thePERSONAL_ACCESS_TOKEN
in theCLA Assistant
action, i.e.,${{ secrets.PERSONAL_ACCESS_TOKEN }}
.dessant/lock-threads@v4
action doesn't require a personal access token, ensured no invalid or unnecessary tokens are being passed to it.These changes should fix the bad credentials error and allow the GitHub Actions to run successfully.