CREDO23 a8292f5dcc Revert "Merge pull request #1649 from CREDO23/kb_git_mvp" ... This reverts commit 366f9c18a, keeping the git-native knowledge base in dev until the issues queued for the next release are fixed. Nothing shipped by that merge was reachable in production: git-native behaviour needs both the KNOWLEDGE_STORE_ENABLED env (default FALSE) and a per-workspace column (default false), so reverting changes no runtime behaviour. Migrations 175 and 176 stay applied in production; alembic_version is moved back to 174 by hand so this tree's upgrade is a no-op. Both revisions only add columns, and they use ADD COLUMN IF NOT EXISTS, so re-landing this work re-applies them harmlessly.		2026-07-31 01:46:56 +02:00
..
alembic	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
app	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
scripts	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
tests	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
.dockerignore	chore(backend): exclude tests/ from production Docker image	2026-05-06 17:16:22 +05:30
.env.example	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
.gitignore	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
.python-version
alembic.ini
celery_worker.py	fix: celery_app path and gmail indexing	2025-10-21 21:11:41 -07:00
Dockerfile	docs(docker): note entrypoint wires xvfb at runtime	2026-07-10 17:17:53 +02:00
main.py	feat: api playground, other tweaks	2026-07-06 16:45:04 -07:00
pyproject.toml	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00
uv.lock	Revert "Merge pull request #1649 from CREDO23/kb_git_mvp"	2026-07-31 01:46:56 +02:00