Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Fix GitHub Actions Failing Due to Bad Credentials #52

Open
wants to merge 3 commits into
base: main
Choose a base branch
from

Conversation

sweep-ai[bot]
Copy link
Contributor

@sweep-ai sweep-ai bot commented Dec 28, 2023

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 error was specifically coming from the dessant/lock-threads@v4 action. The BOT_GITHUB_TOKEN was replaced with the default GITHUB_TOKEN provided by GitHub Actions in the workflow files where it was used.

Summary of Changes

  • Modified .github/workflows/stale.yml to use GITHUB_TOKEN instead of BOT_GITHUB_TOKEN.
  • Modified .github/workflows/release.yml to use GITHUB_TOKEN instead of BOT_GITHUB_TOKEN.
  • If BOT_GITHUB_TOKEN was used in .github/workflows/gosec.yml, it was replaced with GITHUB_TOKEN.
  • Modified .github/workflows/cla.yml to use GITHUB_TOKEN instead of BOT_GITHUB_TOKEN. If REDBOT_GITHUB_TOKEN was also a GitHub token and it was causing issues, it was replaced as well.

These changes should resolve the issue of GitHub Actions failing due to bad credentials.

Copy link
Contributor Author

sweep-ai bot commented Dec 28, 2023

Rollback Files For Sweep

  • Rollback changes to .github/workflows/stale.yml
  • Rollback changes to .github/workflows/stale.yml
  • Rollback changes to .github/workflows/release.yml
  • Rollback changes to .github/workflows/release.yml
  • Rollback changes to .github/workflows/cla.yml
  • Rollback changes to .github/workflows/cla.yml

@sweep-ai sweep-ai bot added the sweep label Dec 28, 2023
Copy link
Contributor Author

sweep-ai bot commented Dec 28, 2023

Sandbox Executions

  • Running GitHub Actions for .github/workflows/stale.yml
Check .github/workflows/stale.yml with contents:

Ran GitHub Actions for d94f8c6b216fb2af1fd160b4a35fb8ccc30bb44d:

  • Running GitHub Actions for .github/workflows/release.yml
Check .github/workflows/release.yml with contents:

Ran GitHub Actions for bc3026d651ca4c7313fd392767307b68aa3ad24a:

  • Running GitHub Actions for .github/workflows/gosec.yml
Check .github/workflows/gosec.yml with contents:
  • Running GitHub Actions for .github/workflows/cla.yml
Check .github/workflows/cla.yml with contents:

Ran GitHub Actions for bcb53dc547816b3cbaa031a1421f41583d943443:

Copy link
Contributor Author

sweep-ai bot commented Dec 28, 2023

Sweeping

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:


Copy link
Contributor Author

sweep-ai bot commented Dec 28, 2023

Sweeping

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

@kubbot kubbot removed the sweep label Dec 30, 2023
@kubbot
Copy link
Member

kubbot commented May 13, 2024

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

@kubbot kubbot added the lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale. label May 13, 2024
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
lifecycle/stale Denotes an issue or PR has remained open with no activity and has become stale.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

2 participants