Hacktoberfest 2026: los issues que los mantenedores marcaron para octubre, abiertos y aptos para principiantes. Explorar issues de Hacktoberfest

PR Update Action

Abierto
  • ¿Algo no está bien?
#9,141 0 comentarios 0 reacciones 3 asignados Ver en GitHub

Los mantenedores suelen responder en 3 días

@KumoLiu ya está trabajando en esto.

Desde el 29/9/2026.

Evaluación

Este issue todavía no se ha evaluado.

Descripción

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?)."
          fi

This 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.

Lenguaje dominante
Python
Estrellas
8.7k
Forks
1.6k
Merge medio
3 d 10 h
PR fusionados (30 d)
18

Preparar el entorno

Primeros pasos

  1. Lee el issue completo y luego la guía de contribución del proyecto.
  2. Comenta en el issue que vas a ocuparte — evita que dos personas hagan lo mismo.
  3. Haz un fork del repositorio y trabaja en una rama.
  4. Abre un pull request que haga referencia al número del issue.

Más de Project-MONAI/MONAI

Todos los issues de Project-MONAI/MONAI

Issues similares

Más issues de Python

Recibe los nuevos issues en tu correo

Un resumen breve de issues de GitHub para principiantes.