Add GitHub Actions Workflow

[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 introduces a new GitHub Actions workflow for the repository. The workflow includes the necessary jobs and steps to build, test, and deploy the application. It also includes a step to run the dessant/lock-threads@v4 action, which is used to automatically lock closed issues and pull requests after a period of inactivity.

The dessant/lock-threads@v4 action is configured with the necessary GitHub token for authentication. The token is accessed in the workflow file as a GitHub Actions secret.

Summary of Changes

• Created a new directory .github/workflows/ at the root of the repository.
• Added a new file .github/workflows/main.yml which defines the GitHub Actions workflow.
• Configured the dessant/lock-threads@v4 action with the necessary GitHub token for authentication.

[sweep-ai-deprecated]

Rollback Files For Sweep

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

[sweep-ai-deprecated]

Sandbox Executions

• Running GitHub Actions for .github/workflows/main.yml ✓

Check .github/workflows/main.yml with contents:

Ran GitHub Actions for 5b712a27d0eda7f4fdc7771dafac77775de76b62:

[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/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

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

Here are the logs: