The autoupdate.yml workflow (chinthakagodawita/autoupdate) runs with PR_FILTER: "auto_merge", so it only rebases PRs that have GitHub auto-merge armed. PRs under review (auto-merge off) fall BEHIND main and are never auto-updated.
Change: drop the auto_merge filter so every open PR is kept up to date as main advances — set PR_FILTER: "all" (the action's default). Update the workflow's header comment, which currently documents the auto-merge-only behaviour and the "held/draft PRs left alone" rationale.
Keep AUTOUPDATE_TOKEN (needed so the update re-triggers the PR's CI) and MERGE_CONFLICT_ACTION: "ignore" (a PR that would conflict on update is skipped, not failed).
The `autoupdate.yml` workflow (`chinthakagodawita/autoupdate`) runs with `PR_FILTER: "auto_merge"`, so it only rebases PRs that have GitHub auto-merge armed. PRs under review (auto-merge off) fall `BEHIND` main and are never auto-updated.
**Change:** drop the `auto_merge` filter so **every** open PR is kept up to date as `main` advances — set `PR_FILTER: "all"` (the action's default). Update the workflow's header comment, which currently documents the auto-merge-only behaviour and the "held/draft PRs left alone" rationale.
Keep `AUTOUPDATE_TOKEN` (needed so the update re-triggers the PR's CI) and `MERGE_CONFLICT_ACTION: "ignore"` (a PR that would conflict on update is skipped, not failed).
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
The
autoupdate.ymlworkflow (chinthakagodawita/autoupdate) runs withPR_FILTER: "auto_merge", so it only rebases PRs that have GitHub auto-merge armed. PRs under review (auto-merge off) fallBEHINDmain and are never auto-updated.Change: drop the
auto_mergefilter so every open PR is kept up to date asmainadvances — setPR_FILTER: "all"(the action's default). Update the workflow's header comment, which currently documents the auto-merge-only behaviour and the "held/draft PRs left alone" rationale.Keep
AUTOUPDATE_TOKEN(needed so the update re-triggers the PR's CI) andMERGE_CONFLICT_ACTION: "ignore"(a PR that would conflict on update is skipped, not failed).