Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[GH-ISSUE #2792] [FEAT]: Feature Request for github import programmatically #1791

New Issue
Closed
opened 2026-02-22 18:26:33 -05:00 by yindo · 1 comment
yindo commented 2026-02-22 18:26:33 -05:00
Owner
Copy Link
Copy Source

Originally created by @olariuromeo on GitHub (Dec 10, 2024).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2792

What would you like to see?

It would be useful if, when importing from GitHub, the user could select the maximum number of requests per hour. This way, if a repository is very large, it could be imported programmatically in multiple steps, as GitHub has a limit. The initial part of the repository could be imported, and then in subsequent hours or days, the task could be completed by updating the import in several stages. This would be particularly helpful for large repositories to manage the import process more efficiently. Additionally, this task could run in the background, and once it is completed, a notification could be displayed to the user. Furthermore, it would be beneficial to have an update option that could also be programmed, allowing for automatic updates when a new version becomes available, for example. Thus, having the ability to maintain multiple versions of a repository would be very useful, enabling users to have different versions of the documents within the repository.

. Additionally, I often encounter the following error:

[collector] error: Error: Unable to fetch repository files: 403 {"message":"API rate limit exceeded for user ID . If you reach out to GitHub Support for help, please include the request ID and timestamp","documentation_url":"[https://docs.github.com/rest/overview/rate-limits-for-the-rest-api","status":"403"}](https://docs.github.com/rest/overview/rate-limits-for-the-rest-api%22,%22status%22:%22403%22%7D) at /app/collector/node_modules/langchain/dist/document_loaders/web/github.cjs:

Originally created by @olariuromeo on GitHub (Dec 10, 2024). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/2792 ### What would you like to see? It would be useful if, when importing from GitHub, the user could select the maximum number of requests per hour. This way, if a repository is very large, it could be imported programmatically in multiple steps, as GitHub has a limit. The initial part of the repository could be imported, and then in subsequent hours or days, the task could be completed by updating the import in several stages. This would be particularly helpful for large repositories to manage the import process more efficiently. Additionally, this task could run in the background, and once it is completed, a notification could be displayed to the user. Furthermore, it would be beneficial to have an update option that could also be programmed, allowing for automatic updates when a new version becomes available, for example. Thus, having the ability to maintain multiple versions of a repository would be very useful, enabling users to have different versions of the documents within the repository. . Additionally, I often encounter the following error: `[collector] error: Error: Unable to fetch repository files: 403 {"message":"API rate limit exceeded for user ID . If you reach out to GitHub Support for help, please include the request ID and timestamp","documentation_url":"[https://docs.github.com/rest/overview/rate-limits-for-the-rest-api","status":"403"}](https://docs.github.com/rest/overview/rate-limits-for-the-rest-api%22,%22status%22:%22403%22%7D) at /app/collector/node_modules/langchain/dist/document_loaders/web/github.cjs:`
yindo added the enhancementfeature request labels 2026-02-22 18:26:33 -05:00
yindo closed this issue 2026-02-22 18:26:33 -05:00
yindo commented 2026-02-22 18:26:33 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Dec 11, 2024):

See my previous comment about cron-related tasks or long running message in your other issue.

@timothycarambat commented on GitHub (Dec 11, 2024): See my previous comment about cron-related tasks or long running message in your other issue.
yindo changed title from [FEAT]: Feature Request for github import programmatically to [GH-ISSUE #2792] [FEAT]: Feature Request for github import programmatically 2026-06-05 14:42:41 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label enhancement feature request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#1791
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?