You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
pnpm drizzle:verify-bootstrap — applied the full migration chain against a fresh database.
pnpm --filter @kilocode/db test -- schema.test.ts --runInBand (7 tests)
pnpm --filter @kilocode/db typecheck
pnpm --filter @kilocode/db lint
pnpm format:changed and git diff --check
Visual Changes
N/A
Reviewer Notes
agent_configs.agent_type still permits the values auto_triage and auto_fix. Removing them from the check constraint requires deleting existing rows of those types first, and the generated migration cannot safely order that cleanup with the constraint change. This is intentionally deferred.
Inert leftovers that can be cleaned manually if desired:
Rows in agent_configs with agent_type = 'auto_triage'.
Auto Triage bot users (kilocode_users.id LIKE 'bot-auto-triage-%') and their organization memberships.
Verified the auto-triage table drop, its removal from user anonymization, and the generated snapshot/journal; no source references to auto_triage_tickets remain and the snapshot diff contains only that table's removal.
Verification notes: repo-wide search shows no remaining application, service, or test references to auto_triage_tickets outside historical migrations, and auto_fix_tickets (the only prior FK holder) was already dropped in 0288. The new snapshot is byte-identical to 0289 apart from deleting the public.auto_triage_tickets entry, and the journal entry (idx 290) follows sequentially. DROP TABLE ... CASCADE matches the repo's existing drop-migration pattern and is harmless here since only the table's self-referencing FK existed.
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Stacked on #8151. Drops the legacy Auto Triage database object now that no code reads it.
auto_triage_tickets(table, indexes, constraints).auto_triage_ticketscleanup from account anonymization.packages/db/src/migrations/0290_common_squirrel_girl.sql.Verification
pnpm drizzle generatepnpm drizzle:verify-bootstrap— applied the full migration chain against a fresh database.pnpm --filter @kilocode/db test -- schema.test.ts --runInBand(7 tests)pnpm --filter @kilocode/db typecheckpnpm --filter @kilocode/db lintpnpm format:changedandgit diff --checkVisual Changes
N/A
Reviewer Notes
agent_configs.agent_typestill permits the valuesauto_triageandauto_fix. Removing them from the check constraint requires deleting existing rows of those types first, and the generated migration cannot safely order that cleanup with the constraint change. This is intentionally deferred.Inert leftovers that can be cleaned manually if desired:
agent_configswithagent_type = 'auto_triage'.kilocode_users.id LIKE 'bot-auto-triage-%') and their organization memberships.