Repository navigation
fix(setup): run worktree setup through mise exec (closes #225) - #226
Merged
Merged
Conversation
orca.yaml's setup and the post-checkout hook must run bin/setup through `mise exec`, so it uses the Ruby that .ruby-version names rather than the global one in Orca's environment. The hook falls back to plain bin/setup where mise isn't on the PATH (CI runners). Red: orca.yaml and the hook run bin/setup directly. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
Orca runs orca.yaml's setup and the post-checkout hook in its own environment, which carries the global mise Ruby (4.0.4) instead of the 4.0.7 that .ruby-version names. There `bundle check` failed, `bundle install` ran on the wrong Ruby, and its gem-installed Bundler wrote its own checksum into Gemfile.lock. Both now run `mise exec -- bin/setup --skip-server`; the hook falls back to plain bin/setup without mise. Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
This was referenced Nov 8, 2026
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.
Closes #225.
Problem. Orca runs
orca.yaml's setup and thepost-checkouthook in its own environment. That environment carries the global mise Ruby (4.0.4), not the 4.0.7 that.ruby-versionnames, so worktree setup ranbundle check/bundle installanddb:prepareon the wrong Ruby. Ruby 4.0.4's gem-installed Bundler 4.0.20 then wrote its own checksum intoGemfile.lock, which is why every Orca worktree started with the lockfile modified. Full diagnosis in #225.Change (maintainer's choice: opinionated shared tool config):
orca.yaml:mise exec -- bin/setup --skip-server..githooks/post-checkout: the same whenmiseis on thePATH; plainbin/setup --skip-serverotherwise (GitHub's runners have no mise).Tests, red first (
526bd11b, then the fix074aafdc):spec/project_config_spec.rb:orca.yamlruns setup throughmise exec.spec/githooks/post_checkout_spec.rb: a stubmiseon thePATHreceivesexec -- bin/setup --skip-server. Withoutmiseon thePATH, setup runs directly. The fallback example passed before the change too; it guards the fallback.End to end, from a
PATHthat resolves Ruby 4.0.4 (as Orca's does):git worktree addthrough the new hook ranmise exec -- bin/setup --skip-server, andGemfile.lockstayed clean.bin/setup --skip-serveron 4.0.4 leftGemfile.lockmodified. On 4.0.4 even a satisfiedbundle checkrewrites the lockfile.PATH,rubyis 4.0.4 andmise exec -- rubyis 4.0.7.Depends on mise reading
.ruby-version: this machine'sidiomatic_version_file_enable_toolsincludesruby. Recent mise versions leave it off by default.The pre-push hook ran the full
bin/cion this head.🤖 Generated with Claude Code