A
Arturo Rojas
Context
We have fully migrated to the GitHub Ocean integration and are actively using it in production across our organization.
:bug: Problem We Are Experiencing
We are experiencing a critical and recurring failure during resync when repositories have a large number of open pull requests (~70–80+).
We understand that the integration currently supports a maxResults parameter to cap the number of closed PRs fetched per repository:
  • kind: pull-request
selector:
query: "true"
states: ["closed"]
maxResults: 50 # ✅ Works for closed PRs
since: 60
However, no equivalent parameter exists for open pull requests — the integration fetches all open PRs unconditionally. When a repository accumulates ~70–80+ open PRs, this causes the integration to fail. We have confirmed that GitHub's own API also struggles under these conditions, but the lack of a configurable limit on the Port side amplifies the problem.
:white_check_mark: What We Are Requesting
We would like a maxResults (or equivalent) parameter for open pull requests, similar to what already exists for closed PRs, so we can cap the number of open PRs fetched per repository.
Example of the configuration we need:
  • kind: pull-request
selector:
query: "true"
states: ["open"]
maxResults: 50 # ✅ REQUESTED — limit open PRs per repo
:briefcase: Business Impact
We are currently manually closing pull requests in GitHub on affected repositories just to stay below the threshold where the integration stops failing. This is not a sustainable solution.
The issue will recur, as those repositories naturally generate a high volume of open PRs.
This is our highest priority limitation with the Ocean integration at this time.
Thank you for considering this request!