Skip to content

fix(repo): clone on configured baseBranch#495

Merged
zbigniewsobiecki merged 1 commit intodevfrom
fix/clone-repo-use-base-branch
Feb 23, 2026
Merged

fix(repo): clone on configured baseBranch#495
zbigniewsobiecki merged 1 commit intodevfrom
fix/clone-repo-use-base-branch

Conversation

@zbigniewsobiecki
Copy link
Copy Markdown
Member

Summary

  • Fix: cloneRepo() now passes --branch to git clone using the project's baseBranch from the database, ensuring agent work always starts from the correct branch (not just GitHub's default)
  • Lint cleanup: Fixed pre-existing noExplicitAny biome warning in ackMessageGenerator.test.ts by using unknown with proper type narrowing
  • Tests: Added test case verifying non-default baseBranch (e.g. develop) is correctly passed through to git clone

Test plan

  • Existing cloneRepo test updated to assert --branch flag presence
  • New test case covers non-default baseBranch (e.g. develop)
  • Full test suite passes (2619 tests, 161 files)
  • Lint and typecheck clean (0 warnings, 0 errors)

🤖 Generated with Claude Code

cloneRepo() always cloned the GitHub default branch, ignoring the
project's baseBranch setting from the database. This meant projects
configured with e.g. baseBranch=develop would still start work from
main. Pass --branch to git clone so the checkout always matches the
project config.

Also fixes a pre-existing lint warning (noExplicitAny) in the ack
message generator test.

Co-Authored-By: Claude Opus 4.6 <noreply@anthropic.com>
@zbigniewsobiecki zbigniewsobiecki merged commit 032cc00 into dev Feb 23, 2026
5 checks passed
@zbigniewsobiecki zbigniewsobiecki deleted the fix/clone-repo-use-base-branch branch February 23, 2026 08:26
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant