Skip to content

fix: use GitHub search API for repo search in modal#657

Open
czhu12 wants to merge 5 commits into
mainfrom
chriszhu__github-search-api
Open

fix: use GitHub search API for repo search in modal#657
czhu12 wants to merge 5 commits into
mainfrom
chriszhu__github-search-api

Conversation

@czhu12

@czhu12 czhu12 commented Jul 6, 2026

Copy link
Copy Markdown
Collaborator

Summary

  • Replace client-side repo filtering with GitHub's search_repos API
  • Previously fetched all user repos (auto_paginate = true) then filtered in Ruby — slow for users with many repos/orgs
  • Now uses GET /search/repositories with in:name fork:true for fast server-side search

Test plan

  • Open repo selection modal, type a search term, verify results appear quickly
  • Verify search finds repos across orgs (not just personal repos)
  • Verify pagination still works when browsing without a search term

🤖 Generated with Claude Code

Chris added 5 commits July 6, 2026 16:07
Instead of fetching all repos with auto_paginate and filtering in Ruby,
use GitHub's search_repos API for server-side filtering. Much faster for
users with many repos or org memberships.
Both repository controllers shared identical index logic. Extract into a
shared concern with provider-specific hooks for client building, search,
and listing.
…sages

Show instructions for both classic and fine-grained PATs on the GitLab
provider form. Detect fine-grained tokens that are missing permissions
and show which specific permissions are needed.
Use DaisyUI tabs to switch between classic and fine-grained token
instructions instead of stacking them. Use smaller, subtler code badges
that don't overflow.
Replace DaisyUI radio tabs with the app's existing tabs Stimulus
controller pattern for consistency.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant