Skip to content

fix: unset GH_TOKEN when empty in run-script workflow #4

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.

Sign up for GitHub

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

Merged
albertodonato merged 1 commit into from
Oct 20, 2026
Merged

fix: unset GH_TOKEN when empty in run-script workflow #4

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 5 additions & 1 deletion .github/workflows/run-script.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -59,7 +59,11 @@ jobs:
key: pre-commit-${{ runner.os }}-${{ hashFiles('.pre-commit-config.yaml') }}

- name: Run
run: ${{ inputs.run }} # zizmor: ignore[template-injection] caller-provided script
# Some tools reject an empty GH_TOKEN (e.g. zizmor), so unset it rather
# than leaving it empty.
run: | # zizmor: ignore[template-injection] caller-provided script
[ -n "$GH_TOKEN" ] || unset GH_TOKEN
${{ inputs.run }}
env:
GH_TOKEN: ${{ inputs.github-token && github.token || '' }}
# Point prek at the pre-commit cache path so the cache step covers both.
Expand Down
Loading