Add check for BOT_GITHUB_TOKEN in lock-issue workflow #36
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
PR Feedback (click)
I created this PR to fix the failing GitHub Actions.## Description
This PR adds a check for the
BOT_GITHUB_TOKEN
secret in thelock-issue.yml
GitHub Actions workflow. This check ensures that the workflow fails early with a clear error message if theBOT_GITHUB_TOKEN
secret is not set. This will make it easier to identify and fix issues related to the GitHub token in the future.The check is implemented as a shell script in a
run
command before the step that uses thedessant/lock-threads@v4
action. The script checks if theBOT_GITHUB_TOKEN
environment variable is set and is not empty. If the check fails, the script prints an error message and exits with a non-zero status to fail the workflow.Summary of Changes
BOT_GITHUB_TOKEN
secret is set in thelock-issue.yml
workflow.