Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

feat(chat): Add follow up questions functionality #2241

Merged
merged 1 commit into from
Feb 22, 2024
Merged

Conversation

StanGirard
Copy link
Collaborator

This pull request adds the ability to ask follow up questions in the chat. It also includes various code improvements and bug fixes.

Copy link

vercel bot commented Feb 22, 2024

The latest updates on your projects. Learn more about Vercel for Git ↗︎

Name Status Preview Comments Updated (UTC)
quivrapp ✅ Ready (Inspect) Visit Preview 💬 Add feedback Feb 22, 2024 8:22pm

@StanGirard StanGirard changed the title Add follow up questions functionality feat(chat): Add follow up questions functionality Feb 22, 2024
@StanGirard StanGirard merged commit 5f862e7 into main Feb 22, 2024
3 of 6 checks passed
StanGirard added a commit that referenced this pull request Feb 22, 2024
StanGirard added a commit that referenced this pull request Feb 22, 2024
🤖 I have created a release *beep* *boop*
---


## 0.0.210 (2024-02-22)

## What's Changed
* feat: Update memory allocation in task definition by @StanGirard in
#2243
* fix: get_brain_details API to include user_id parameter by @StanGirard
in #2242
* feat(chat): Add follow up questions functionality by @StanGirard in
#2241
* Reduce sampling rate for Sentry traces by @StanGirard in
#2245
* Revert "feat(chat): Add follow up questions functionality" by
@StanGirard in #2246
* Add max_input and max_tokens parameters to KnowledgeBrainQA
constructor by @StanGirard in #2247


**Full Changelog**:
v0.0.209...v0.0.210

---
This PR was generated with [Release
Please](https://github.com/googleapis/release-please). See
[documentation](https://github.com/googleapis/release-please#release-please).
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

1 participant