Skip to content

Repository navigation

[BUG](ci) Open uv-lock-refresh PRs as overture-pull-requester #732

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
John McCall (lowlydba) merged 3 commits into from
Sep 11, 2026
Merged

[BUG](ci) Open uv-lock-refresh PRs as overture-pull-requester #732

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
ed48a66
fix(ci): open uv-lock-refresh PRs as overture-pull-requester
lowlydba Sep 10, 2026
c9d4f38
fix(ci): match overture-pull-requester noreply address to rebase-vnex…
lowlydba Sep 10, 2026
dd38453
Merge branch 'main' into lowlydba-fix-ci-failure
lowlydba Sep 10, 2026
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
23 changes: 17 additions & 6 deletions .github/workflows/uv-lock-refresh.yml
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -23,9 +23,22 @@ jobs:
name: Refresh uv.lock
runs-on: ubuntu-slim
permissions:
contents: write # create-pull-request pushes the refresh branch
pull-requests: write # create-pull-request opens/updates the PR
contents: read
steps:
# The default GITHUB_TOKEN can't clear the required "OMF PR Check" linked-issue
# check -- a scheduled lockfile refresh has no issue to link. The
# overture-pull-requester app (same one rebase-vnext.yaml uses) has a
# bypass for that, so open the PR as the app instead; this also means the PR
# triggers CI normally, unlike a GITHUB_TOKEN-authored PR.
- name: Generate app token
id: app-token
uses: actions/create-github-app-token@bcd2ba49218906704ab6c1aa796996da409d3eb1 # v3.2.0
with:
client-id: Iv23liiN80WEARreTV7m
private-key: ${{ secrets.OVERTURE_PULL_REQUESTER_APP_PEM }} # zizmor: ignore[secrets-outside-env]
permission-contents: write
permission-pull-requests: write

- uses: actions/checkout@3d3c42e5aac5ba805825da76410c181273ba90b1 # v7.0.1
with:
persist-credentials: false
Expand All @@ -36,18 +49,16 @@ jobs:

- run: uv lock --upgrade

# NOTE: PRs opened with the default GITHUB_TOKEN do not trigger other
# workflows, so CI won't run on this PR. Provide a PAT/App token via
# `token:` if the lockfile refresh needs to be gated on CI before merge.
# create-pull-request stages the diff, commits, pushes a branch, and
# opens/updates the PR idempotently; a gh pr create script would
# re-implement that and need persisted checkout credentials to push.
- uses: peter-evans/create-pull-request@5f6978faf089d4d20b00c7766989d076bb2fc7f1 # v8.1.1
with: # zizmor: ignore[superfluous-actions]
token: ${{ steps.app-token.outputs.token }}
commit-message: |
[CHORE](deps) refresh uv.lock

Signed-off-by: github-actions[bot] <41898282+github-actions[bot]@users.noreply.github.com>
Signed-off-by: overture-pull-requester[bot] <overture-pull-requester[bot]@users.noreply.github.com>
branch: uv-lock-refresh
Comment thread
lowlydba marked this conversation as resolved.
title: "[CHORE](deps) weekly uv.lock refresh"
labels: "bot,automation 🦾"
Expand Down
Loading