Mintplex-Labs/anything-llm
1
0
Fork 0
mirror of https://github.com/Mintplex-Labs/anything-llm.git synced 2026-07-19 14:13:35 -04:00
Code Issues 328 Packages Projects Releases 10 Wiki Activity

[PR #3771] [CLOSED] Thread archive and recovery feature #4394

New Issue
Closed
opened 2026-02-22 18:35:44 -05:00 by yindo · 0 comments
yindo commented 2026-02-22 18:35:44 -05:00
Owner
Copy Link
Copy Source

📋 Pull Request Information

Original PR: https://github.com/Mintplex-Labs/anything-llm/pull/3771
Author: @17ColinMiPerry
Created: 5/6/2025
Status: ❌ Closed

Base: master ← Head: thread-archive-feature

📝 Commits (3)

  • cd9ecd4 implemented archival for threads
  • a2cd691 Merge branch 'master' into thread-archive-feature
  • 64d765e cleaned up comments

📊 Changes

7 files changed (+343 additions, -23 deletions)

View changed files

📝 frontend/src/components/Sidebar/ActiveWorkspaces/ThreadContainer/ThreadItem/index.jsx (+89 -14)
📝 frontend/src/components/Sidebar/ActiveWorkspaces/ThreadContainer/index.jsx (+153 -8)
📝 frontend/src/models/workspaceThread.js (+37 -0)
📝 server/endpoints/workspaceThreads.js (+40 -0)
📝 server/models/workspaceThread.js (+1 -1)
➕ server/prisma/migrations/20250503010020_workspace_threads_add_archived/migration.sql (+22 -0)
📝 server/prisma/schema.prisma (+1 -0)

📄 Description

Pull Request Type

  • ✨ feat
  • 🐛 fix
  • ♻️ refactor
  • 💄 style
  • 🔨 chore
  • 📝 docs

Relevant Issues

resolves #3214

What is in this change?

The archived thread feature allows users to archive threads from there workspace. These threads can then either be recovered or permanently deleted from an Archived Threads dropdown.

Additional Information

Database Changes

Added an archived boolean field to the workspace_threads table

Backend Changes

Added new endpoints in workspaceThreads.js (restore and archive) to handle restoring and archiving threads

Frontend Changes

Implemented a dropdown that appears on hover if archived threads exist that allow for viewing and recovering/deleting archived threads

Developer Validations

  • I ran yarn lint from the root of the repo & committed changes
  • Relevant documentation has been updated
  • I have tested my code functionality
  • Docker build succeeds locally

🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.

## 📋 Pull Request Information **Original PR:** https://github.com/Mintplex-Labs/anything-llm/pull/3771 **Author:** [@17ColinMiPerry](https://github.com/17ColinMiPerry) **Created:** 5/6/2025 **Status:** ❌ Closed **Base:** `master` ← **Head:** `thread-archive-feature` --- ### 📝 Commits (3) - [`cd9ecd4`](https://github.com/Mintplex-Labs/anything-llm/commit/cd9ecd4a53daef9cd90f02d0b111149c05481d4d) implemented archival for threads - [`a2cd691`](https://github.com/Mintplex-Labs/anything-llm/commit/a2cd691900a5e72c8221d809c5f8b33ed6f93f28) Merge branch 'master' into thread-archive-feature - [`64d765e`](https://github.com/Mintplex-Labs/anything-llm/commit/64d765e4628b8dd603c11987102c49ddf30ffe9b) cleaned up comments ### 📊 Changes **7 files changed** (+343 additions, -23 deletions) <details> <summary>View changed files</summary> 📝 `frontend/src/components/Sidebar/ActiveWorkspaces/ThreadContainer/ThreadItem/index.jsx` (+89 -14) 📝 `frontend/src/components/Sidebar/ActiveWorkspaces/ThreadContainer/index.jsx` (+153 -8) 📝 `frontend/src/models/workspaceThread.js` (+37 -0) 📝 `server/endpoints/workspaceThreads.js` (+40 -0) 📝 `server/models/workspaceThread.js` (+1 -1) ➕ `server/prisma/migrations/20250503010020_workspace_threads_add_archived/migration.sql` (+22 -0) 📝 `server/prisma/schema.prisma` (+1 -0) </details> ### 📄 Description ### Pull Request Type <!-- For change type, change [ ] to [x]. --> - [x] ✨ feat - [ ] 🐛 fix - [ ] ♻️ refactor - [ ] 💄 style - [ ] 🔨 chore - [ ] 📝 docs ### Relevant Issues <!-- Use "resolves #xxx" to auto resolve on merge. Otherwise, please use "connect #xxx" --> resolves #3214 ### What is in this change? <!-- Describe the changes in this PR that are impactful to the repo. --> The archived thread feature allows users to archive threads from there workspace. These threads can then either be recovered or permanently deleted from an Archived Threads dropdown. ### Additional Information <!-- Add any other context about the Pull Request here that was not captured above. --> #### Database Changes Added an archived boolean field to the workspace_threads table #### Backend Changes Added new endpoints in workspaceThreads.js (restore and archive) to handle restoring and archiving threads #### Frontend Changes Implemented a dropdown that appears on hover if archived threads exist that allow for viewing and recovering/deleting archived threads ### Developer Validations <!-- All of the applicable items should be checked. --> - [x] I ran `yarn lint` from the root of the repo & committed changes - [x] Relevant documentation has been updated - [x] I have tested my code functionality - [x] Docker build succeeds locally --- <sub>🔄 This issue represents a GitHub Pull Request. It cannot be merged through Gitea due to API limitations.</sub>
yindo added the pull-request label 2026-02-22 18:35:44 -05:00
yindo changed title from [PR #3771] Thread archive and recovery feature to [PR #3771] [CLOSED] Thread archive and recovery feature 2026-06-05 15:18:21 -04:00
yindo closed this issue 2026-06-05 15:18:21 -04:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
Desktop
Docker
Integration Request
Integration Request
OS: Linux
OS: Mobile
OS: Windows
UI/UX
blocked
bug
bug
core-team-only
documentation
duplicate
embed-widget
enhancement
feature request
github_actions
good first issue
investigating
needs info / can't replicate
possible bug
pull-request
Mirrored from GitHub Pull Request
 question
stage: specifications
wontfix
No Label pull-request
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
yindo
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: Mintplex-Labs/anything-llm#4394
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?