Allow a different rebase branch from the repository default branch via cli flag or config

[rodionlim]

If there is a long-lived develop branch, is it possible that we set develop as the default base branch for the rebase step? Right now, it seems like we have to change the upstream repository's default branch for that behaviour to work automatically.

[kunchenguid]

Thanks for raising this - it's a clean, sensible ask. Supporting a configurable rebase base (e.g. a long-lived develop branch) without having to repoint the upstream's default branch makes sense, and we'd like to add it.

Accepted onto the backlog as an enhancement - it'll land as a config/CLI option on the rebase step. Appreciate the suggestion.

[Dhara159]

+1 on this — a long-lived develop branch is exactly our setup.

One thing worth confirming as this is implemented: the same config/CLI option should also drive the PR base/target branch, not just the rebase base. Today both derive from the stored default_branch (auto-detected from the remote's default at init), so pr.go opens PRs against main even when the team integrates on develop. Ideally one setting controls both, with precedence like: --base flag > repo config > global config > auto-detected default.

It'd also help if the value survived no-mistakes init — the only current workaround (editing repos.default_branch in state.sqlite) gets reset by UpdateRepoMetadata on re-init.