adds AI summary tab#2674
Closed
zanynik wants to merge 1 commit intostackernews:masterfrom
Closed
Conversation
|
Review the following changes in direct dependencies. Learn more about Socket for GitHub.
|
Member
|
welcome to the repo. if you want a feature, the best thing to do is propose it and let us decide if we want it or not, then we'll welcome prs for it. i don't want this feature nor do I want a dep on some cloud model. |
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Description
A clear and concise description of what you changed and why.
Adds AI summary tab. (LLMs are best known for good summarization & linking sources - I think it can be used to better guide discussion which sometimes can get lost in a huge nest of comments.)
Screenshots
Additional Context
Was anything unclear during your work on this PR? Anything we should definitely take a closer look at?
The API Key is in .env.local , which is obviously not uploaded. So in production, a decision has to be made on which AI and API KEY will be used. Current version uses GEMINI API KEY.
Checklist
Are your changes backward compatible? Please answer below:
YES
For example, a change is not backward compatible if you removed a GraphQL field or dropped a database column.
On a scale of 1-10 how well and how have you QA'd this change and any features it might affect? Please answer below:
YES
For frontend changes: Tested on mobile, light and dark mode? Please answer below:
YES
Did you introduce any new environment variables? If so, call them out explicitly here:
GEMINI_API_KEY
Did you use AI for this? If so, how much did it assist you?
YES