extensions
extensions copied to clipboard
[GitHub] Cache repositories for faster search
Extension – GitHub
Author:
Describe the feature and the current behavior/state.
When I search repositories, the extension currently always seems to hit the Github API. The results never show up immediately, but it takes a couple of seconds, even for searches I have done before. I would be really nice if the extension would remember/cache my own repositories (also the private ones) so that it can show those immediately when searching.
After showing the cached/remembered repositories, it should still keep searching and refreshing the data to remove any stale repos
Who will benefit with this feature?
Any user that wants to access their own repos quickly
Hi @DandyDev 👋 This extension may meet your needs. GitHub Repository Search
Hi @DandyDev 👋 This extension may meet your needs. GitHub Repository Search
I tried that one, but it will search through all Github repositories. I only want to search through my own
I would also love this functionality. 95% of the time I'm searching through my own repos or the repos of the orgs I'm associated with. Having those results faster and prioritized at the top would make a huge difference.
Is this something the Raycast developers can look into?
We could add a dropdown to the GitHub Repository Search extension to either search all or only your repositories?!
@thomaspaulmann that would be great! Than I can switch to that extension. Does Github Repository Search cache my own repos? Because that is the core of the issue for performance :)
It caches the repos that you visit. So if you visited a repo once (regardless if it's your own or another one), it will stay in recently visited repos. And it has actions to open the PR, issues, and other pages of a repo directly. Give it a try and let me know how you like it.
We could add a dropdown to the GitHub Repository Search extension to either search all or only your repositories?!
Added in here: https://github.com/raycast/extensions/pull/2266
This issue/pull request has been automatically marked as stale because it has not had recent activity. It will be closed if no further activity occurs in the next 7 days to keep our backlog clean. Thanks for your contributions.