When working with OpenWebUI's knowledge base feature and Git repositories, the system doesn't automatically detect and update files when switching between different Git branches. This creates inconsistency between the actual codebase being referenced and the knowledge base content, leading to potential confusion and incorrect context during conversations.
Implement an automatic file update mechanism that:
Monitors Git branch changes in connected repositories
Automatically refreshes the knowledge base content when a branch switch is detected
Updates file references and embeddings to match the current branch's content
Provides a notification or status indicator when updates are in progress
Maintains conversation history while updating the underlying knowledge base
This feature would be particularly valuable for development teams that:
Work across multiple branches simultaneously
Need to maintain accurate context when discussing different versions of code
Use feature branches for development
Require branch-specific documentation and context
The implementation should be efficient and avoid unnecessary reprocessing of unchanged files while ensuring the knowledge base stays synchronized with the current Git branch.
Originally created by @dallenpyrah on GitHub (Dec 20, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7981
# Feature Request
When working with OpenWebUI's knowledge base feature and Git repositories, the system doesn't automatically detect and update files when switching between different Git branches. This creates inconsistency between the actual codebase being referenced and the knowledge base content, leading to potential confusion and incorrect context during conversations.
Implement an automatic file update mechanism that:
- Monitors Git branch changes in connected repositories
- Automatically refreshes the knowledge base content when a branch switch is detected
- Updates file references and embeddings to match the current branch's content
- Provides a notification or status indicator when updates are in progress
- Maintains conversation history while updating the underlying knowledge base
This feature would be particularly valuable for development teams that:
- Work across multiple branches simultaneously
- Need to maintain accurate context when discussing different versions of code
- Use feature branches for development
- Require branch-specific documentation and context
The implementation should be efficient and avoid unnecessary reprocessing of unchanged files while ensuring the knowledge base stays synchronized with the current Git branch.
Blocking a user prevents them from interacting with repositories, such as opening or commenting on pull requests or issues. Learn more about blocking a user.
Originally created by @dallenpyrah on GitHub (Dec 20, 2024).
Original GitHub issue: https://github.com/open-webui/open-webui/issues/7981
Feature Request
When working with OpenWebUI's knowledge base feature and Git repositories, the system doesn't automatically detect and update files when switching between different Git branches. This creates inconsistency between the actual codebase being referenced and the knowledge base content, leading to potential confusion and incorrect context during conversations.
Implement an automatic file update mechanism that:
This feature would be particularly valuable for development teams that:
The implementation should be efficient and avoid unnecessary reprocessing of unchanged files while ensuring the knowledge base stays synchronized with the current Git branch.