Skip to content

Squash-Merging through API mangles commit body #14241

Open
@soulmerge

Description

@soulmerge
  • Gitea version (or commit ref): 1.13.0
  • Git version: 2.20.1
  • Operating system: debian

Description

When using the API to merge a pull request, we have the option to specify a commit body when performing a squash merge. Gitea appends its default content for the commit message body ("co-authored by", etc.) to the string specified as MergeMessageField.

I think using this default is fine if this field is not provided at all, but I would expect the commit message to just contain the string I provided to the API, even if it is an empty string.

Alternatively, the the API could provide a flag to disable this behaviour explicitly.

Metadata

Metadata

Assignees

No one assigned

    Labels

    issue/needs-feedbackFor bugs, we need more details. For features, the feature must be described in more detailmodifies/apiThis PR adds API routes or modifies themtype/enhancementAn improvement of existing functionality

    Type

    No type

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions