docs(migrations): correct VCS index migration range in 216_vcs_integration comment (MUL-3772)

After renumbering the VCS migrations to 216-221, the header comment still
referenced the pre-renumber index range (214-218). The indexes now live at
217-221. Comment-only; no SQL change.

Co-authored-by: multica-agent <github@multica.ai>
This commit is contained in:
Bohan-J
2026-07-24 15:28:26 +08:00
parent 3c94bd189c
commit 3380e487e5

View File

@@ -17,7 +17,7 @@
-- rows below in a single atomic statement). The inline UNIQUE / PRIMARY KEY
-- constraints stay — they back the ON CONFLICT upsert targets in vcs.sql.
-- Secondary indexes live in follow-up single-statement CREATE INDEX
-- CONCURRENTLY migrations (214-218), which cannot share a file with these
-- CONCURRENTLY migrations (217-221), which cannot share a file with these
-- CREATE TABLEs.
CREATE TABLE IF NOT EXISTS vcs_connection (