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(frontend): UI / UX Notifications #2826

Merged
merged 11 commits into from
Jul 10, 2024
Merged

feat(frontend): UI / UX Notifications #2826

merged 11 commits into from
Jul 10, 2024

Conversation

Zewed
Copy link
Collaborator

@Zewed Zewed commented Jul 10, 2024

Description

Please include a summary of the changes and the related issue. Please also include relevant motivation and context.

Checklist before requesting a review

Please delete options that are not relevant.

  • My code follows the style guidelines of this project
  • I have performed a self-review of my code
  • I have commented hard-to-understand areas
  • I have ideally added tests that prove my fix is effective or that my feature works
  • New and existing unit tests pass locally with my changes
  • Any dependent changes have been merged

Screenshots (if appropriate):

Copy link

vercel bot commented Jul 10, 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 Jul 10, 2024 3:01pm

@dosubot dosubot bot added size:XL This PR changes 500-999 lines, ignoring generated files. area: frontend Related to frontend functionality or under the /frontend directory labels Jul 10, 2024
@Zewed Zewed merged commit 6056450 into main Jul 10, 2024
4 checks passed
@Zewed Zewed deleted the feat/moveNotifToLeft branch July 10, 2024 15:13
StanGirard added a commit that referenced this pull request Jul 11, 2024
🤖 I have created a release *beep* *boop*
---


## 0.0.281 (2024-07-11)

## What's Changed
* feat: quivr core minimal chat by @AmineDiro in
#2803
* chore: Add release-please-core workflow and configuration files by
@StanGirard in #2809
* chore(main): release core 0.0.2 by @StanGirard in
#2812
* chore(main): release core 0.0.2 by @StanGirard in
#2813
* chore(main): release core 0.0.2 by @StanGirard in
#2814
* chore(main): release core 0.0.2 by @StanGirard in
#2815
* fix(pyproject): fixed to quivr github by @StanGirard in
#2816
* chore(main): release core 0.0.3 by @StanGirard in
#2817
* feat: quivr core minimal chat by @AmineDiro in
#2818
* chore(main): release core 0.0.4 by @StanGirard in
#2819
* feat: Add GitHub Actions workflow for running tests on backend/core by
@StanGirard in #2820
* feat: Add GitHub Actions workflow for running tests on backend/core by
@StanGirard in #2822
* feat(precommit): Update pre-commit hooks to latest versions by
@StanGirard in #2823
* feat: quivr core chat history by @AmineDiro in
#2824
* chore(main): release core 0.0.5 by @StanGirard in
#2821
* feat(frontend): UI / UX Notifications by @Zewed in
#2826
* feat: quivr-core ask streaming by @AmineDiro in
#2828
* chore(main): release core 0.0.6 by @StanGirard in
#2829
* fix: llm model name by @AmineDiro in
#2830
* chore(main): release core 0.0.7 by @StanGirard in
#2831
* feat: Add Quivr chatbot example by @StanGirard in
#2827
* feat(renovate): updated configuration by @StanGirard in
#2835
* feat: Update aiofiles dependency to loosen version control by
@StanGirard in #2834
* chore(main): release core 0.0.8 by @StanGirard in
#2832
* chore: Update quivr-core and chainlit versions in requirements.txt by
@StanGirard in #2836


**Full Changelog**:
v0.0.280...v0.0.281

---
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
area: frontend Related to frontend functionality or under the /frontend directory size:XL This PR changes 500-999 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

1 participant