Fix GitHub Actions Failure Due to Bad Credentials

[sweep-ai-deprecated]

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 GitHub Actions failing due to bad credentials. The problem was traced back to the gh tool not being properly authenticated during the workflow run.

The solution implemented in this PR is to add a step in the GitHub Actions workflow to authenticate the gh tool using a token stored in a GitHub secret. This ensures that the gh tool is properly authenticated before it is used in subsequent steps of the workflow.

Summary of Changes

• Added a new step in the .github/workflows/main.yml workflow file to authenticate the gh tool. This step runs the command gh auth login --with-token < ${{ secrets.GH_TOKEN }}.
• The new authentication step is set to only run when the GH_TOKEN secret is available. This is controlled by an if condition: if: secrets.GH_TOKEN != ''.

Please note that for this fix to work, a new repository secret named GH_TOKEN needs to be added in the repository settings. This secret should contain the gh authentication token.

[sweep-ai-deprecated]

Rollback Files For Sweep

• Rollback changes to .github/workflows/main.yml

[sweep-ai-deprecated]

Sandbox Executions

[sweep-ai-deprecated]

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-deprecated]

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)