Type
Bug
Scope
Multi-theme or Platform
Skillset
dev ops
Description
.github/workflows/uv-lock-refresh.yml now opens its PR successfully (after #729), but the PR is stuck: #730 has every check green except issue / "Check for linked issue", which is required and fails because a scheduled lockfile refresh has no linked issue to point at.
The overture-pull-requester GitHub App (already used in rebase-vnext.yaml for the vnext force-push, client-id Iv23liiN80WEARreTV7m, PEM in secrets.OVERTURE_PULL_REQUESTER_APP_PEM) has a branch-protection/required-check bypass that the default GITHUB_TOKEN doesn't. Opening the uv-lock-refresh PR as that app instead of GITHUB_TOKEN should let it clear the "OMF PR Check" linked-issue requirement the same way the vnext rebase does.
Fix: generate an app token via actions/create-github-app-token (same client-id/secret as rebase-vnext.yaml) and pass it to both actions/checkout and peter-evans/create-pull-request in uv-lock-refresh.yml, in place of the implicit GITHUB_TOKEN.
Type
Bug
Scope
Multi-theme or Platform
Skillset
dev ops
Description
.github/workflows/uv-lock-refresh.ymlnow opens its PR successfully (after #729), but the PR is stuck: #730 has every check green exceptissue/ "Check for linked issue", which is required and fails because a scheduled lockfile refresh has no linked issue to point at.The
overture-pull-requesterGitHub App (already used inrebase-vnext.yamlfor the vnext force-push, client-idIv23liiN80WEARreTV7m, PEM insecrets.OVERTURE_PULL_REQUESTER_APP_PEM) has a branch-protection/required-check bypass that the defaultGITHUB_TOKENdoesn't. Opening theuv-lock-refreshPR as that app instead ofGITHUB_TOKENshould let it clear the "OMF PR Check" linked-issue requirement the same way the vnext rebase does.Fix: generate an app token via
actions/create-github-app-token(same client-id/secret asrebase-vnext.yaml) and pass it to bothactions/checkoutandpeter-evans/create-pull-requestinuv-lock-refresh.yml, in place of the implicitGITHUB_TOKEN.