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

[GH-ISSUE #105] Add a way to update docs #72

New Issue
Closed
opened 2026-02-22 18:17:46 -05:00 by yindo · 6 comments
yindo commented 2026-02-22 18:17:46 -05:00
Owner
Copy Link
Copy Source

Originally created by @danglingptr0x0 on GitHub (Jun 23, 2023).
Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/105

Hey,

I have recently tried updating a doc, but ended up with creating a new one instead, which did have the same name, but the id after the name differed. As such, I had to manually remove the original and then embed the new one. There could be a way to simply overwrite (after confirming such action in a modal) a file that has the same name within a given workspace.

Thank you

Originally created by @danglingptr0x0 on GitHub (Jun 23, 2023). Original GitHub issue: https://github.com/Mintplex-Labs/anything-llm/issues/105 Hey, I have recently tried updating a doc, but ended up with creating a new one instead, which did have the same name, but the id after the name differed. As such, I had to manually remove the original and then embed the new one. There could be a way to simply overwrite (after confirming such action in a modal) a file that has the same name within a given workspace. Thank you
yindo closed this issue 2026-02-22 18:17:46 -05:00
yindo commented 2026-02-22 18:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@AntonioCiolino commented on GitHub (Jun 23, 2023):

i want this too, but keep in mind when you change the doc, you have to re-embed it anyway - so it's going to get a new guid/name.

@AntonioCiolino commented on GitHub (Jun 23, 2023): i want this too, but keep in mind when you change the doc, you have to re-embed it anyway - so it's going to get a new guid/name.
yindo commented 2026-02-22 18:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@danglingptr0x0 commented on GitHub (Jun 24, 2023):

i want this too, but keep in mind when you change the doc, you have to re-embed it anyway - so it's going to get a new guid/name.

@AntonioCiolino Yes, but the process could be more streamlined, not requiring manual removal of the old doc. It could be an optional switch.

@danglingptr0x0 commented on GitHub (Jun 24, 2023): > i want this too, but keep in mind when you change the doc, you have to re-embed it anyway - so it's going to get a new guid/name. @AntonioCiolino Yes, but the process could be more streamlined, not requiring manual removal of the old doc. It could be an optional switch.
yindo commented 2026-02-22 18:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@timothycarambat commented on GitHub (Jun 25, 2023):

This is something that would be a massive breakthrough in the space (and something we have a solution for) so that you can more easily manage and modify documents in place without a re-embed totally.

@timothycarambat commented on GitHub (Jun 25, 2023): This is something that would be a massive breakthrough in the space (and something we have a solution for) so that you can more easily manage and modify documents in place without a re-embed totally.
yindo commented 2026-02-22 18:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@mrlopezco commented on GitHub (Mar 9, 2024):

@timothycarambat
Is there a solution for this? Whenever I upload the same document per API, or a github repo, it always creates a new file.

image

@mrlopezco commented on GitHub (Mar 9, 2024): @timothycarambat Is there a solution for this? Whenever I upload the same document per API, or a github repo, it always creates a new file. ![image](https://github.com/Mintplex-Labs/anything-llm/assets/22092667/e9068b3b-02c8-414d-89e9-8f6458cb6a0e)
yindo commented 2026-02-22 18:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@atljoseph commented on GitHub (Apr 26, 2024):

I’m so confused. This seems like a feature request. The repo author agreed it is a good idea. They said there was a solution. Then, the issue was closed without outlining what the solution is, or where the feature went in terms of roadmap. A little more context would be appreciated. It would complement the product nicely.

@atljoseph commented on GitHub (Apr 26, 2024): I’m so confused. This seems like a feature request. The repo author agreed it is a good idea. They said there was a solution. Then, the issue was closed without outlining what the solution is, or where the feature went in terms of roadmap. A little more context would be appreciated. It would complement the product nicely.
yindo commented 2026-02-22 18:17:46 -05:00
Author
Owner
Copy Link
Copy Source

@danglingptr0x0 commented on GitHub (Apr 27, 2024):

I’m so confused. This seems like a feature request. The repo author agreed it is a good idea. They said there was a solution. Then, the issue was closed without outlining what the solution is, or where the feature went in terms of roadmap. A little more context would be appreciated. It would complement the product nicely.

Agreed

@danglingptr0x0 commented on GitHub (Apr 27, 2024): > I’m so confused. This seems like a feature request. The repo author agreed it is a good idea. They said there was a solution. Then, the issue was closed without outlining what the solution is, or where the feature went in terms of roadmap. A little more context would be appreciated. It would complement the product nicely. Agreed
yindo changed title from Add a way to update docs to [GH-ISSUE #105] Add a way to update docs 2026-06-05 14:33:19 -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
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#72
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?