Import from Github issues doesn't respect the Base branch and sets it to master automatically

[genesiscz]

Checklist

• I searched existing issues and this hasn't been reported

Area

Not sure

Operating System

macOS

Version

2.7.2-beta.10

What happened?

Steps to reproduce

1. In Project Settings > GitHub > Default Branch - base branch for creating worktrees to "dev"
2. Go to Tools > GitHub Issues > Create Task > Create Task From Issue
3. Go to Kanban Board and Start the task
4. The worktree gets created from the master branch
5. Even if I edit the task before starting it, I am not able to set the GitHub Base branch as I am when I Create a new task directly.

Expected behavior

The Task gets the correct base branch

Logs / Screenshots

[github-actions]

👋 Thanks for opening your first issue!

A maintainer will triage this soon. In the meantime:

• Make sure you've provided all the requested info
• Join our Discord for faster help

[joelfuller2016]

@openhands-agent Please fix this GitHub import base branch bug.

Issue Summary: When importing tasks from GitHub Issues, the base branch setting from Project Settings is ignored. Tasks created via "Create Task From Issue" always use master as the base branch instead of the configured default (e.g., dev).

Platform: macOS, v2.7.2-beta.10

Steps to Reproduce:

1. Set Project Settings > GitHub > Default Branch to "dev"
2. Go to Tools > GitHub Issues > Create Task > Create Task From Issue
3. Start the task from Kanban Board
4. Observe: worktree created from master, not dev

Additional Context:

• Editing the task before starting doesn't show the base branch field
• Manually creating a task shows the base branch field correctly

Investigation Areas:

1. apps/frontend/src/ - GitHub issue import UI components
2. apps/backend/ - Task creation from GitHub issue handler
3. Check where base_branch is read from project settings vs hardcoded
4. Compare code path for "Create Task From Issue" vs manual task creation

Required Fix:

1. Find where GitHub issue import creates task metadata
2. Ensure base_branch is read from project settings, not hardcoded to master
3. Add base branch field to task edit dialog if missing
4. Verify worktree creation uses the correct base branch

Target Branch: develop

[genesiscz]

I see that even if I created the Task manually, it creates the worktree incorrectly:

It merged the dev branch to it as a first commit but that might be a thing claude did, not what the orchestrator/app itself did.