Filter by reset
- Everywhere
85 - Issues
23 - Pull Requests
18 - Comments
44
Enable all full-text search operators
Migrate to per-repo storage scheme
Enable operators for keyword search and disable query sanitizer
Add license and related fixes and improvements
We need to address the following issues: Add the missing license Investigate indexer issues as something is malfunctioning Optimize frontend performance by implementing lazy loading for images Add multiple repo links on the main page after search input
Possibility to search across all repositories of the organization
We need to add the ability to search across all the organization's repositories. This shouldn't trigger a reindexing of all repos, but it should enable searching through all the organization's data. We'll need to modify the structure to make this happen …
Search across all organization's repositories
Enable all full-text search operators
Replace "Vector search" with "Semantic search" in the demo
Rename 'Vector Search' to 'Semantic Search'. Prepare and upload a new database dump containing only vector embeddings for our repositories. This will make it lighter and easier to get started.
Enable all full-text search operators
Update to separate table per organization schema
Enable all full-text search operators
Change internal architecture of storing data
We should migrate to a system where we store each organization in a separate table. This approach will allow us to maintain the logic for searching one, two, or multiple repositories within a single organization. It will also help us narrow down query …
Change internal architecture of storing data
Show comments on state filter change for those issue state only (JOIN in the demo)
When we work with filters and search, we can currently filter by the state that only issues and pull requests have. However, when we change the state to open or close, we still search for comments everywhere. As discussed before, it would be a good idea …
size_S
Change internal architecture of storing data
Update README with clear instruction of how to deploy
Change internal architecture of storing data
Change internal architecture of storing data
Empty list when adding a repository to the github demo
We should investigate why the list is empty on production servers but works correctly in the local environment.
Change internal architecture of storing data
Implement the query suggestion logic
We should design and display query suggestions in the same way Google does, and use the latest code from Buddy to accomplish this. The user input should bounce with a slight delay, and with almost every keystroke, we should render and display a popup …
Implement the query suggestion logic
Prevent 100k+ repos to be added
Since we aim for this GitHub issue search to be a demo project, there may be issues with big repositories due to indexing that takes a long time and consumes a lot of memory. To be fair and make it best suited as a demo project, we should set limits and …
est::size_S
Implement the query suggestion logic
We need to consider and implement a way to configure and toggle fuzzy search options in the user interface. We should be able to: Turn fuzzy search on or off Enable or disable different keyboard layouts Potentially adjust other fuzziness settings
We should add the latest update from Buddy to work with the Manticore GitHub demo. This will allow us to validate its quality on a large dataset and assess how fast it is. The purpose of this integration is to use the latest version of Buddy and make …
Experiment with distributed table
Try to use a distributed table with issue and comment tables in it and CALL AUTOCOMPLETE on it to validate whether it works as expected or not.
Demo: change closed issue/PR color to github's