-
Notifications
You must be signed in to change notification settings - Fork 3
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
Add check for BOT_GITHUB_TOKEN secret in lock-issue workflow #22
base: main
Are you sure you want to change the base?
Conversation
Rollback Files For Sweep
|
Sandbox Executions
Check .github/workflows/lock-issue.yml with contents: |
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: Making changes according to plan... (step 2/3) |
PR Feedback (click)
I created this PR to fix the failing GitHub Actions.## Description
This PR adds a check at the beginning of the lock-issue workflow that ensures the BOT_GITHUB_TOKEN secret is present. If the secret is not present, the workflow will fail with a clear error message. This change is intended to prevent the workflow from failing with a "Bad credentials" error if the BOT_GITHUB_TOKEN secret is missing.
The check is implemented as a new step at the beginning of the workflow that runs a shell command to check if the BOT_GITHUB_TOKEN environment variable is set. If the environment variable is not set, the shell command exits with a non-zero status code, which causes the workflow to fail.
Summary of Changes