[CI] Replace the PR Limit workflow with the .asf.yaml pull request creation cap

Describe the enhancement requested

pr_limit.yml (added in #51200) closes pull requests from contributors without repository access once they have more than 3 open at the same time. It can be replaced by the .asf.yaml's creation_cap, so GitHub's native pull request creation cap can now be configured in .asf.yaml:

github:
  pull_requests:
    creation_cap:
      enabled: true
      max_open_pull_requests: 3
      include_drafts: true

However GitHub's cap only exempts users with write access. Current workflow also exempted triage collaborators (the collaborators list in .asf.yaml). apache/infrastructure-asfyaml#135 adds a bypass_users list to creation_cap that would let us keep exempting them, but it is still open.

Component(s)

Continuous Integration

Thanks for opening this, I think this is a good idea as long as we can bypass relevant people as a few folks who have legitimate reasons for having multiple PRs open have been hit by the limit recently.

Hi folks! In case if it helps, yesterday (https://github.blog/changelog/2026-10-28-pull-request-limits-exempt-contributors-by-age-or-history/) GitHub improved their own PR limit implementation and added a number of exemption criteria (e.g. by account age, or by number of merged PRs):

Also, this issue is related to #54696

We should do this to remove the current pull_request_target event on the workflow, see:

[CI] Remove pull_request_target event workflows #55392

@krassowski

Merged pull requests: Exempt contributors who have had at least the number of pull requests you set merged in that repository.

This is great! We'd no longer need to use collaborators workaround. I'll include it here. Thanks @krassowski

We should do this to remove the current pull_request_target event on the workflow, see:

Didn't look into this yet. Is it something we can do with this PR?

Didn't look into this yet. Is it something we can do with this PR?

Yes, if we rely on the .asf.yaml configuration the whole workflow will be removed so no more pull_request_target event needed.

apacheGH-55163: [CI] Replace the PR Limit workflow with the .asf.yaml…

@rok

@rok Since apache/infrastructure-asfyaml#135 has also been merged, we can use the bypass_users functionality as well to exempt collaborators from the PR limit.

@Reranko05

@Reranko05 Added to #55164, please review :).

@krassowski

Opened apache/infrastructure-asfyaml#146 for @krassowski's suggestion.

GH-55163: [CI] Replace the PR Limit workflow with the .asf.yaml pull …

Issue resolved by pull request 55164
#55164

The deploy seems to have failed. I've received the following email:

An error occurred while processing the github feature in .asf.yaml:

while parsing a mapping
  in "arrow.git/.asf.yaml::github", line 35, column 1:
        # https://arrow.apache.org/d ...
    ^ (line: 35)
unexpected key not in schema 'bypass_users'
  in "arrow.git/.asf.yaml::github", line 43, column 1:
        - EnricoMi
    ^ (line: 43)

---
With regards, ASF Infra.
For further information, please see the .asf.yaml documentation at:
https://github.com/apache/infrastructure-asfyaml/blob/main/README.md

I've opened an issue to INFRA as it seems the bypass_users isn't yet deployed into production.
https://issues.apache.org/jira/browse/INFRA-28628

Navigation Menu

Repository navigation

[CI] Replace the PR Limit workflow with the .asf.yaml pull request creation cap #55163

Describe the enhancement requested

Component(s)

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

[CI] Replace the PR Limit workflow with the .asf.yaml pull request creation cap #55163

Description

Describe the enhancement requested

Component(s)

Activity

thisisnic commented on Oct 23, 2026

krassowski commented on Oct 29, 2026

raulcd commented on Nov 4, 2026

rok commented on Nov 4, 2026

raulcd commented on Nov 4, 2026

Reranko05 commented on Nov 4, 2026

rok commented on Nov 4, 2026

rok commented on Nov 4, 2026

raulcd commented on Nov 5, 2026

raulcd commented on Nov 5, 2026

Metadata

Metadata

Assignees

Labels

Type

Projects

Milestone

Relationships

Development

Issue actions