Repository navigation
PR Update Automation #9141
Description
Is your feature request related to a problem? Please describe.
When PRs are approved they need their branches to be manually kept up to date with the state of dev, this is a bottleneck issue in getting more PRs through because we can't automate a pipeline. The solution is to use an action to update the PRs when dev gets pushed. This should update only the oldest PR which is both approved and has automerge enabled. These two properties together can thus be used by maintainers to signify a PR is ready to be eventually merged, there shouldn't every be many of these so it's not going to create ordering confusion, but will stop working if a PR is help up with test fails. This is an alternative to merge queues.
Describe the solution you'd like
The action below is derived from this test which automates this process:
name: Auto-Update PRs
on:
push:
branches:
- main # Change to your primary target branch (e.g., dev)
workflow_dispatch: # Allows manual triggering if needed
permissions:
contents: write
pull-requests: write
jobs:
update-prs:
runs-on: ubuntu-latest
steps:
- name: Checkout target branch
uses: actions/checkout@v6
with:
fetch-depth: 0 # Fetches all history so branches can be merged locally
- name: Update the oldest PR which is approved and automerging-enabled
env:
GH_TOKEN: ${{ secrets.PAT_UPDATE_TOKEN }}
run: |
# Find all open PRs targeting this branch which are open and approved
PR_DATA=$(gh pr list --state open --search 'review:approved' --base ${{ github.ref_name }} --json number,reviewDecision,autoMergeRequest)
echo '================================'
echo "PR_DATA:"
echo $PR_DATA
echo '================================'
# select the oldest open approved PR with automerge enabled
OLDEST_APPROVED=$(echo $PR_DATA | jq -r '.[] | select(.reviewDecision == "APPROVED") | select(.autoMergeRequest != null) | "\(.number)"'|head -n 1)
if [ -z "$OLDEST_APPROVED" ]
then
echo "No approved PRs to update."
else
echo "Updating PR $OLDEST_APPROVED ..."
gh pr update-branch "$OLDEST_APPROVED" || echo "Failed to update PR #$OLDEST_APPROVED (merge conflicts?)."
fiThis critically relies on a personal access token (PAT) being set to PAT_UPDATE_TOKEN which has read/write permissions for Contents and PullRequests (and maybe Actions as well). This won't work with GITHUB_TOKEN since approval will be required to run the actions in each updated PR and so obviate the point of the exercise.
The possible plan then is to PR this action in and setup a PAT to provide the permissions, though whose PAT is the question to answer. This stems from a recent change to Github security rules.
The alternative is to try merge queues and see how they work, see #8991 and Merge Queue Docs.
Activity
ericspod commentedon Oct 12, 2026
The alternative to an action or merge queues is to just run the script locally within a MONAI clone directory and the
ghcli tool installed:This will try to update exactly one PR, so any with blocking issues will be skipped to hopefully allow one to eventually be merged in the background. This can be left running continuously with
while true; do ./autoupdate.sh; sleep 1800;doneto try the script every half hour.[-]PR Update Action[/-][+]PR Update Automation[/+]