Type
Bug
Scope
Multi-theme or Platform
Skillset
dev ops
Description
#732 fixed the required "OMF PR Check" linked-issue check for uv-lock-refresh PRs by opening them as the overture-pull-requester app instead of GITHUB_TOKEN. The follow-up PR, #739, now clears that check but fails DCO instead.
peter-evans/create-pull-request's author input defaults to ${{ github.actor }} (the user who triggered the run) when not set explicitly, not the app token's identity. #739 was opened via a manual workflow_dispatch, so the commit author became the triggering user while the Signed-off-by trailer still said overture-pull-requester[bot], an author/signoff mismatch that fails DCO.
Fix: pin author: and committer: on the create-pull-request step to overture-pull-requester[bot] <overture-pull-requester[bot]@users.noreply.github.com>, matching the Signed-off-by trailer, so this doesn't vary by trigger actor.
Type
Bug
Scope
Multi-theme or Platform
Skillset
dev ops
Description
#732 fixed the required "OMF PR Check" linked-issue check for
uv-lock-refreshPRs by opening them as theoverture-pull-requesterapp instead ofGITHUB_TOKEN. The follow-up PR, #739, now clears that check but fails DCO instead.peter-evans/create-pull-request'sauthorinput defaults to${{ github.actor }}(the user who triggered the run) when not set explicitly, not the app token's identity. #739 was opened via a manualworkflow_dispatch, so the commit author became the triggering user while theSigned-off-bytrailer still saidoverture-pull-requester[bot], an author/signoff mismatch that fails DCO.Fix: pin
author:andcommitter:on thecreate-pull-requeststep tooverture-pull-requester[bot] <overture-pull-requester[bot]@users.noreply.github.com>, matching theSigned-off-bytrailer, so this doesn't vary by trigger actor.