[feat]: Starting a new conversation in a project should pull before making the worktree

[QuinnBast]

Feature Summary

Currently, it seems like when you click "+" to start a new conversation in EmDash, it will just make a worktree off of what the current directory has checked out. Sometimes this might be out of date, or be a working branch that the user is on for development.

The IDE should both:

1. Attempt to pull the latest main or master branch; and
2. Create the worktree off of the repository's primary branch.

Problem or Use Case

Currently, it doesn't seem to pull or fetch the latest changes when starting a new conversation which means after completing work, and then starting a new conversation, it is not aware of any new work that was completed due to the lack of pulling/fetching.

Proposed Solution

In order to do this maybe EmDash needs to be able to have user's configure their repository on setup to indicate what the name of their primary branch is?

Alternatives Considered

No response

Additional Context

No response

[honarewto-a11y]

This makes sense — creating a new conversation from an outdated or non‑primary branch can definitely cause confusion.
Pulling the latest changes and basing the worktree on the repository’s primary branch (main/master) would provide a much more predictable workflow.
Configuring the primary branch during setup also sounds like a clean solution.
Following the discussion.

[QuinnBast]

Closed as not planned with no discussions? Wut

[arnestrickmann]

@QuinnBast sorry for that. We closed this accidentally:)

[jschwxrz]

we should not automatically pull before creating a new task from a local branch. git pull mutates the user’s checked-out local branch. It can create merge commits, trigger rebase behavior, fail on conflicts or otherwise change repository state the user did not ask us to change. also the user may intentionally want to create a task from the current local branch, even if it is stale relative to the remote.

that is why emdash supports creating tasks from remote branches. if the user selects a remote branch like origin/main, emdash fetches the remote-tracking ref and creates the task branch from that ref. that gives the new task the latest remote state without pulling into or mutating local main.

when creating a new project, emdash also sets the projects default branch to the remote default branch, so new tasks are created from the fetched remote default branch by default and therefore not stale.