Can this help in explaining how the code works, its schematics or HLD of a given github repo ?
Show HN: GitHub-assistant – Natural language questions from your GitHub data
11–17 of 17 posts
Re: Show HN: GitHub-assistant – Natural language questions from your GitHub data
#12Earlier quoted context omitted.
Same thoughts
We pull data from the GitHub API which includes data that that is not available from GitHub.com pages. Currently only PR, Issues, Commit and Star data is being loaded. You can also read more here https://medium.com/relta/github-assistant-49ae388ad758
Re: Show HN: GitHub-assistant – Natural language questions from your GitHub data
#13Earlier quoted context omitted.
We pull data from the GitHub API which includes data that that is not available from GitHub.com pages. Currently only PR, Issues, Commit and Star data is being loaded. You can also read more here https://medium.com/relta/github-assistant-49ae388ad758
There will new data from the graphql API added over time. Would love your feedback on which data you like to see added https://docs.github.com/en/graphql
Re: Show HN: GitHub-assistant – Natural language questions from your GitHub data
#14Pretty nifty, is Relta going to be OSS as well?
Re: Show HN: GitHub-assistant – Natural language questions from your GitHub data
#15Pretty nifty, is Relta going to be OSS as well?
Yes in the future. We share the source code in both commercial and non-commercial engagements already. Drop me a line at amir [at] relta.dev if interested.
[0] - https://popsia.com
Re: Show HN: GitHub-assistant – Natural language questions from your GitHub data
#16Earlier quoted context omitted.
There will new data from the graphql API added over time. Would love your feedback on which data you like to see added https://docs.github.com/en/graphql
Maybe a better question: What questions could be answered with your service, that could not be answered with just cURL + Git + the GitHub API?
- The GitHub graphql API limits to 100 items to be queried at a time and has pretty opaque secondary rate limits. Building this with cURL would take effort. dlt handles all this complexity to set up a robust pipeline by providing a connector to the GitHub API. - Creating semantic layers manually from a relational dataset and leveraging it in a text-to-sql pipeline to prevent hallucinations (similar to those we highlighted in our Medium post) would take lots of manual effort, which Relta streamlines. - Creating a chat front-end with charts was made easy by assistant-ui
Hope this makes sense.