fix: gracefully handle missing workspace.branch column after OpenCode v2 migration - #22
Open
bet4it wants to merge 1 commit into
Open
fix: gracefully handle missing workspace.branch column after OpenCode v2 migration#22bet4it wants to merge 1 commit into
bet4it wants to merge 1 commit into
Conversation
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
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
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.
Running OpenCode v2 applies a
workspace_domainmigration that replaces theworkspacetable columns with provider bindings, removing thebranchcolumn. The old code only checked for the table's existence, so after a v2 run the querySELECT w.branchfails with "no such column". Switch topragma_table_info('workspace')to check for thebranchcolumn itself, matching the existing pattern used for theversioncolumn in the same file. When the column is absent the branch info is simply omitted (git_branch = None), which is consistent with how Codex, Cursor, Kimi, Pi, and other providers behave.