Skip to content

fix: use the requirements bot token to open the OpenAPI schema PR #39188

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
feanil merged 1 commit into from
Oct 5, 2026
Merged

fix: use the requirements bot token to open the OpenAPI schema PR #39188

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
7 changes: 7 additions & 0 deletions .github/workflows/generate_openapi_schemas.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -134,6 +134,13 @@ jobs:
- name: Open pull request if schemas changed
uses: peter-evans/create-pull-request@5f6978faf089d4d20b00c7766989d076bb2fc7f1 # v8
with:
# The default GITHUB_TOKEN is scoped to this repository and cannot
# resolve org teams, so requesting team-reviewers with it fails this
# step after the PR is already open; PRs it opens also start no CI.
# upgrade-python-requirements.yml uses the requirements bot token for
# the same reason. Forks have no such secret and fall back to the
# default token.
token: ${{ secrets.REQUIREMENTS_BOT_GITHUB_TOKEN || github.token }}
branch: chore/update-openapi-schemas
# Without a suffix, a run that happens while the previous PR is
# still open pushes onto that same branch. Matches
Expand Down
Loading