-
Notifications
You must be signed in to change notification settings - Fork 52
Feature Request: Manual Codebase Reindexing #171
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
Comments
How does reindexing work now? Or is there no reindexing for GitHub repos at all, so once it's indexed it's kept as-is? |
@Piedone Gurubase automatically checks for added, removed, or changed files and reindexes them every 12 hours |
Ah OK. I think that should be good enough for most projects. |
I agree with @Piedone that this should be sufficient. I think nonetheless that extending the REST API (and UI) to trigger reindexing on demand fits well given that this is possible for other sources. For the ITB Guru we've wired up our CI processes to reindex automatically sources that have been updated which in my view is a win-win: sources are immediately up to date, and there is no need to reindex if not needed, nor to reindex everything when only specific pages have changed. |
Just like the reindexing feature for other data sources, we should consider adding it for GitHub codebases as well. Requested by @costas80.
The text was updated successfully, but these errors were encountered: