Skip to content

Revert "[CI] Use custom token for 'Update pre-commit hooks' job" #794

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
aobolensk merged 1 commit into from
Jun 4, 2026
Merged

Revert "[CI] Use custom token for 'Update pre-commit hooks' job" #794

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
2 changes: 1 addition & 1 deletion .github/workflows/update-pre-commit.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -22,4 +22,4 @@ jobs:
- name: Update pre-commit hooks
uses: ./.github/actions/update-precommit
with:
token: ${{ secrets.PRECOMMIT_UPDATE_TOKEN }}
token: ${{ secrets.GITHUB_TOKEN }}

@chatgpt-codex-connector chatgpt-codex-connector Bot Jun 4, 2026

Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Preserve automatic CI runs for generated update PRs

When the scheduled job creates or updates the PR through .github/actions/update-precommit/action.yml, authenticating with GITHUB_TOKEN prevents its push events from starting workflows and leaves resulting pull_request workflow runs awaiting manual approval. Consequently, the generated pre-commit update PR no longer automatically runs the checks configured in .github/workflows/main.yml and the other pull_request workflows; retaining the custom token is necessary for fully automatic validation.

Useful? React with 👍 / 👎.

Loading