3 ms·

Is there any information you can get out of this that isn't already available in the GitHub.com UI? I tried asking things like "What could the most interesting

by diggan 2y ago

Is there any information you can get out of this that isn't already available in the GitHub.com UI? I tried asking things like "What could the most interesting information you can tell me about this repository?" but it seems like most of the data is already available in the UI in pretty much the same format, except you click a link to see it instead of writing a question and waiting for a reply.

eddywebs 2y ago
Same thoughts
- aazo11 2y ago
  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 https://medium.com/relta/github-assistant-49ae388ad758
  - aazo11 2y ago
    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 https://docs.github.com/en/graphql
    - diggan 2y ago
      Maybe a better question: What questions could be answered with your service, that could not be answered with just cURL + Git + the GitHub API?
      - aazo11 2y ago
        Great question! The purpose of github-assistant is to showcase the technologies that make it easy to build a tool/feature like this, not necessarily for it to be a stand-alone service. With dlt/Relta/LangGraph/assistant-ui we spin this up in about 10 days. For example: - 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.

by diggan 2y ago

eddywebs 2y ago

Same thoughts

aazo11 2y ago
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 https://medium.com/relta/github-assistant-49ae388ad758
- aazo11 2y ago
  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 https://docs.github.com/en/graphql
  - diggan 2y ago
    Maybe a better question: What questions could be answered with your service, that could not be answered with just cURL + Git + the GitHub API?
    - aazo11 2y ago
      Great question! The purpose of github-assistant is to showcase the technologies that make it easy to build a tool/feature like this, not necessarily for it to be a stand-alone service. With dlt/Relta/LangGraph/assistant-ui we spin this up in about 10 days. For example: - 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.