Skip to content

Add more results to GitHub App repository listing #1941

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Open
wants to merge 1 commit into
base: develop
Choose a base branch
from

Conversation

asosso
Copy link

@asosso asosso commented Apr 29, 2025

Problem

We noticed that when 30 repositories are registered with the GitHub App, adding a 31st repository causes one of the existing ones (often the latest) to be removed.

https://diggertalk.slack.com/archives/C01DVJRK6CX/p1745923260568589

Root cause

By default, the GitHub API returns a limited number of results per request (usually 30). Since the call to client.Apps.ListRepos did not explicitly handle pagination, we were unintentionally working with a truncated list of repositories.

Quick fix

We now explicitly provide pagination options using github.ListOptions{Page: 1, PerPage: 100} to ensure the API returns up to 100 repositories.
This is a temporary fix, as the implementation should ideally retrieve all Git repositories.

Summary by CodeRabbit

  • Bug Fixes
    • Improved repository listing to display up to 100 accessible repositories when connecting a GitHub App.

Copy link
Contributor

coderabbitai bot commented Apr 29, 2025

Walkthrough

The change updates the GitHub repository listing logic in the GithubAppCallbackPage handler. Instead of passing a nil options parameter to the client.Apps.ListRepos method, the code now explicitly constructs and passes a github.ListOptions struct with Page: 1 and PerPage: 100. This ensures the API call retrieves up to 100 repositories from the first page. No other logic, error handling, or exported entities are altered.

Changes

File(s) Change Summary
backend/controllers/github.go Updated the GitHub App repository listing to use explicit pagination options (Page: 1, PerPage: 100) instead of passing nil to the API call.

Poem

A hop to GitHub, a leap through code,
Now paging through repos—one hundred in load!
With options set clear, the handler’s delight,
Listing the first page, from morning till night.
🐇✨


📜 Recent review details

Configuration used: CodeRabbit UI
Review profile: CHILL
Plan: Pro

📥 Commits

Reviewing files that changed from the base of the PR and between e03f303 and aec055d.

📒 Files selected for processing (1)
  • backend/controllers/github.go (1 hunks)
🔇 Additional comments (1)
backend/controllers/github.go (1)

2417-2418: Implement full pagination instead of a single‐page quick fix.

Right now we hardcode Page: 1, PerPage: 100 which caps the listing at 100 repos. For installations with more than 100 repositories, this still falls short. To reliably retrieve all repositories, loop through pages using the Response.NextPage value:

-   opt := &github.ListOptions{Page: 1, PerPage: 100}
-   listRepos, _, err := client.Apps.ListRepos(context.Background(), opt)
-   repos := listRepos.Repositories
+   var allRepos []*github.Repository
+   opt := &github.ListOptions{Page: 1, PerPage: 100}
+   for {
+       result, resp, err := client.Apps.ListRepos(context.Background(), opt)
+       if err != nil {
+           slog.Error("Failed to list existing repositories", "installationId", installationId64, "error", err)
+           c.String(http.StatusInternalServerError, "Failed to list existing repos: %v", err)
+           return
+       }
+       allRepos = append(allRepos, result.Repositories...)
+       if resp.NextPage == 0 {
+           break
+       }
+       opt.Page = resp.NextPage
+   }
+   repos := allRepos

This ensures you collect every page until NextPage == 0.
[ suggest_essential_refactor ] [ offer_assistance ]

✨ Finishing Touches
  • 📝 Generate Docstrings

Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai generate sequence diagram to generate a sequence diagram of the changes in this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

CodeRabbit Configuration File (.coderabbit.yaml)

  • You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
  • Please see the configuration documentation for more information.
  • If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/schema.v2.json

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

Copy link
Contributor

@greptile-apps greptile-apps bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

PR Summary

Implemented pagination options in GithubAppCallbackPage to increase repository listing limit from 30 to 100, addressing immediate truncation issues in GitHub App repository registration.

  • Modified client.Apps.ListRepos call in /backend/controllers/github.go to use github.ListOptions{Page: 1, PerPage: 100}
  • Current fix is temporary and needs enhancement to handle pagination for >100 repositories
  • Consider adding a warning or limit indicator when approaching 100 repository limit
  • Recommend implementing proper pagination handling in future updates to support unlimited repositories

💡 (1/5) You can manually trigger the bot by mentioning @greptileai in a comment!

1 file(s) reviewed, 1 comment(s)
Edit PR Review Bot Settings | Greptile

Comment on lines +2417 to +2418
opt := &github.ListOptions{Page: 1, PerPage: 100}
listRepos, _, err := client.Apps.ListRepos(context.Background(), opt)
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

logic: This only retrieves the first 100 repositories. Need to implement pagination to handle orgs with >100 repos.

Suggested change
opt := &github.ListOptions{Page: 1, PerPage: 100}
listRepos, _, err := client.Apps.ListRepos(context.Background(), opt)
opt := &github.ListOptions{Page: 1, PerPage: 100}
var repos []*github.Repository
for {
listRepos, resp, err := client.Apps.ListRepos(context.Background(), opt)
if err != nil {
slog.Error("Failed to list existing repositories",
"installationId", installationId64,
"page", opt.Page,
"error", err,
)
c.String(http.StatusInternalServerError, "Failed to list existing repos: %v", err)
return
}
repos = append(repos, listRepos.Repositories...)
if resp.NextPage == 0 {
break
}
opt.Page = resp.NextPage
}

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