infiniflow / infiniflow/ragflow
[Feature Request]: Could a version management be added to the knowledge base?
Open
Nobody has claimed this yet.
💞 feature
- Dominant language
- Go
- Stars
- 91k
- Forks
- 10.8k
- Avg merge
- 1d 14h
- Merged PRs (30d)
- 705
Description
Self Checks
- I have searched for existing issues search for existing issues, including closed ones.
- I confirm that I am using English to submit this report (Language Policy).
- Non-english title submitions will be closed directly ( 非英文标题的提交将会被直接关闭 ) (Language Policy).
- Please do not modify this template :) and fill in all the required fields.
Is your feature request related to a problem?
Could a version management be added to the knowledge base?
Describe the feature you'd like
Could a version management be added to the knowledge base?
Describe implementation you've considered
Could a version management be added to the knowledge base?
Documentation, adoption, use case
Could a version management be added to the knowledge base?
Additional information
Could a version management be added to the knowledge base?
Contributor guide
No contributing guide indexed for this repository
First steps
- Read the whole issue, then the project's contributing guide.
- Comment on the issue to say you are picking it up — it saves two people doing the same work.
- Fork the repository and make your change on a branch.
- Open a pull request that references the issue number.
Research direction
The issue does not identify files, tests, or an entry point. First clarify what version management means for the knowledge base, including the user workflow and required behavior. Done should be defined by agreed requirements and acceptance criteria.
Written by the indexing model from the issue text.
Assessment
- Domain
- data
- Issue type
- Feature
- Difficulty
- 5/5
- Estimated time
- Over a week
- Activity status
- Stale
- Clarity
- Needs clarification
- Newbie friendliness
- 20/100