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 failing GitHub Actions due to bad credentials. The error was thrown by the dessant/lock-threads@v4 action in the lock-issue.yml workflow file. The issue was caused by an invalid or insufficiently privileged GitHub token being used.

The changes in this PR replace the invalid token with a valid one that has the necessary permissions. The token is stored as a secret in the repository settings and is referenced in the workflow file.

Summary of Changes

• Modified .github/workflows/lock-issue.yml to replace the invalid GitHub token with a valid one in the dessant/lock-threads@v4 action.

[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 eb9f279d8435ef5a760101838cbfe87c9b234e35:

[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/github-project-automation-plus@v0.8.3
yielded the following error:
##[error]Bad credentials

Here are the logs:

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 contributor-assistant/github-action@v2.3.1
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

Generating plan by analyzing files... (step 2/3)

[kubbot]

This issue is stale because it has been open 60 days with no activity.