Skip to content

Tracking: adopt commit/PR streaming end-to-end in downstream consumers #1337

@ognis1205

Description

@ognis1205

Is there an existing issue or pull request for this?

  • I have searched the existing issues and pull requests

Feature description

The remote layer was recently refactored to expose commits and pull requests as streams (PR #1272). While this clears the way for smarter request strategies and performance improvements, the downstream code
still eagerly collects these streams into Vecs and processes them in a non-streaming fashion.

As a result, the current implementation does not yet benefit from:

  • early exits
  • reduced API requests

In other words, the streaming abstraction is not yet reflected end-to-end.

Desired solution

Adopt streaming semantics throughout downstream consumers so that commit and pull request data can be processed incrementally instead of being fully materialized upfront.

This issue is intended as a tracking issue, and the work can be implemented incrementally across multiple follow-up PRs.

Alternatives considered

  • Keeping the current eager collection approach and relying on pagination limits or higher rate limits
  • mplementing ad-hoc early-exit logic on top of fully collected result sets

These alternatives do not fully realize the benefits enabled by the stream-based remote refactor.

Additional context

Related PR: #1272

Metadata

Metadata

Assignees

No one assigned

    Labels

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions