Skip to content

Allow configuring default Pull Request base branch (repo-level or user-level) #36412

@tototomate123

Description

@tototomate123

Problem

Gitea always defaults new Pull Requests to the repository default branch (usually main).
In repositories that use a long-lived integration branch (e.g. dev) and only merge to main for releases, this causes unnecessary friction.

Proposed solution

Add a configurable default PR base branch, either repository-level (e.g. "Default PR target branch") or user-level (preferred base branch per repo).

(This setting should only affect the initial PR creation UI and not change branch protection, merge rules, or existing behavior.)

This matches common workflows where main is protected and dev is the primary integration branch.

(Implemented in #36425)

Metadata

Metadata

Assignees

No one assigned

    Labels

    type/proposalThe new feature has not been accepted yet but needs to be discussed first.

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions