Skip to content

chore(ci): use CLIENT_PIPELINE PAT for generated PRs#500

Merged
Nelson-PROIA merged 4 commits intomainfrom
ci/client-pipeline-pat
Apr 30, 2026
Merged

chore(ci): use CLIENT_PIPELINE PAT for generated PRs#500
Nelson-PROIA merged 4 commits intomainfrom
ci/client-pipeline-pat

Conversation

@Nelson-PROIA
Copy link
Copy Markdown
Contributor

The default GITHUB_TOKEN does not trigger downstream workflows (loop prevention), so generated PRs currently land without CI runs. Switching to the CLIENT_PIPELINE PAT restores CI on those PRs.

The default GITHUB_TOKEN does not trigger downstream workflows
(loop prevention), so generated PRs currently land without CI runs.
Switching to the CLIENT_PIPELINE PAT restores CI on those PRs.
Nelson-PROIA and others added 3 commits April 29, 2026 10:41
…eam CI

The align-version job pushes a follow-up commit to the bot's PR branch.
Without a PAT, actions/checkout uses the default GITHUB_TOKEN, and
subsequent pushes don't trigger pull_request: synchronize events,
leaving the PR HEAD without lint/test/run_examples checks visible.

Pass CLIENT_PIPELINE to actions/checkout so the push uses the PAT and
the downstream CI workflows fire on the new HEAD commit.
So the git push uses the PAT and any subsequent push to the PR branch
triggers pull_request: synchronize. Same fix pattern as the
align-version step.
@Nelson-PROIA Nelson-PROIA merged commit 46c1b98 into main Apr 30, 2026
6 checks passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants