Skip to main content
Version: 3.2.0

GitHub connection test timing out on large organizations

Version: 3.2.0 Date: 2026-11-17

Goal: Test connection listed hundreds of repositories and then failed at 10 seconds, before the backend finished paging the organization.

Solution: After the first page, the remaining pages are requested together, five at a time, and never past the last page GitHub reports. Personal and collaborator repos stay on GET /user/repos; organization repos are not downloaded a second time. The connection test streams progress (Listing repositories… 600) with the number of repositories received so far, and no total. The client waits up to 60 seconds for that listing.

Files Modified:

  • src/protocol/source/github/github.service.ts - fetch remaining pages in parallel and report a running count
  • src/protocol/source/github/github.service.spec.ts - cover the last-page limit and the running count
  • src/protocol/source/source.service.ts - forward listing progress for GitHub
  • src/app.controller.ts - stream discover progress to the connection test
  • ui/src/protocol/tower.api.ts - read the GitHub discover stream and wait up to 60 seconds
  • ui/src/pages/workflows/stepForms/StepInitForm.tsx - show how many repositories have arrived
  • docs/user/configuration/sources.md - describe the running count during Test connection
  • docs/user/fr/configuration/sources.md - same note in French

Release fragment: fix-github-discover-progress