We loaded FalkorDB's GitHub into FalkorDB: Now it explains itself
We chose the dataset where a wrong answer would get caught fastest: a year of FalkorDB's own GitHub history, loaded into FalkorDB. Ask Aevion "Who knows the falkordb-py client code best?" and it names five people, starting with gkorland, who authored 5 merged PRs in that code and reviewed 4. Under the answer is the graph walk behind every name, 20 nodes and 27 edges, from each person to the pull…
FalkorDB loaded its own GitHub history into FalkorDB, creating a graph representation of the repository's activity over the past year. This graph contains 20,961 nodes and 80,642 edges, including 3,544 pull requests, 2,326 issues, and 8,607 comments. The nodes represent files, pull requests, and people, while the edges show relationships such as who authored or reviewed each pull request.
The graph includes special nodes called Components and Decisions. Components are directory prefixes in the repository, like src/udf in FalkorDB core. Each File node is linked to its Component node. Decisions are choices made in pull request or issue threads, linked to the specific code changes and associated comments.
The scoring system assigns points to authors and reviewers of merged pull requests based on various factors like recency and the number of comments on the PR. These points are calculated in real-time using Cypher queries, and the results are cached for quick retrieval. The answer provided by the FalkorDB system is based on the most relevant decisions and their supporting evidence.
Written by urgent.news from Dev.to's reporting — not their text. Machine-written — may contain errors; check the original before relying on it.
