Fix GitHub Actions failure due to bad credentials

[sweep-ai]

PR Feedback (click)

• 👍 Sweep Did Well
• 👎 Sweep Needs Improvement
  I created this PR to fix the failing GitHub Actions.## Description
  This PR addresses the issue of the GitHub Actions workflow failing due to bad credentials. The workflow in question is the one defined in the .github/workflows/lock-issue.yml file. This workflow uses the dessant/lock-threads@v4 action, which requires a GitHub token to function. The token is provided via the github-token input parameter, which was previously set to use the BOT_GITHUB_TOKEN secret.

The error message "Bad credentials" indicated that the BOT_GITHUB_TOKEN secret was either not set or contained an invalid GitHub token. To resolve this, the github-token input parameter has been updated to use a different secret that contains a valid GitHub token.

Summary of Changes

• Modified the .github/workflows/lock-issue.yml file to change the github-token input parameter to use the GITHUB_TOKEN secret.

[sweep-ai]

Rollback Files For Sweep

• Rollback changes to .github/workflows/lock-issue.yml
• Rollback changes to .github/workflows/lock-issue.yml

[sweep-ai]

Sandbox Executions

• Running GitHub Actions for .github/workflows/lock-issue.yml ✓

Check .github/workflows/lock-issue.yml with contents:

Ran GitHub Actions for 43fc86297e0c898fba977c8f3de4dcf20af20184:

[sweep-ai]

Fixing PR: track the progress here.

I'm currently fixing this PR to address the following:

[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:

The command:
Run contributor-assistant/[email protected]
yielded the following error:
##[error]graphql call to get the committers details failed: HttpError: Bad credentials

Here are the logs:
CLA Assistant GitHub Action bot has started the process

Making changes according to plan... (step 3/3)

[sweep-ai]

Fixing PR: track the progress here.

I'm currently fixing this PR to address the following:

[Sweep GHA Fix] The GitHub Actions run failed with the following error logs:

The command:
Run alex-page/[email protected]
yielded the following error:
##[error]Bad credentials

Here are the logs:

Making changes according to plan... (step 3/3)