Squash Merge will generate duplicate commit messages #6445

New Issue

GiteaMirror · 2025-11-02T06:56:13-06:00

GiteaMirror commented

2025-11-02 06:56:13 -06:00

Originally created by @ffbh123456 on GitHub (Dec 3, 2020).

Please see the picture below. Squash Merge will generate two identical commit messages. I think it’s enough to have one of this message. When I use square merge on github, only one commit message will be generated.

Originally created by @ffbh123456 on GitHub (Dec 3, 2020). Please see the picture below. Squash Merge will generate two identical commit messages. I think it’s enough to have one of this message. When I use square merge on github, only one commit message will be generated.  ![image](https://user-images.githubusercontent.com/20750357/101026936-75b24400-35b2-11eb-91c0-3a52571ce1d7.png) ![image](https://user-images.githubusercontent.com/20750357/101027069-9c707a80-35b2-11eb-82d3-4fafb003e2a9.png)

GiteaMirror added the type/enhancement label 2025-11-02 06:56:13 -06:00

GiteaMirror closed this issue

2025-11-02 06:56:13 -06:00

GiteaMirror commented

2025-11-02 06:56:14 -06:00

@ffbh123456 commented on GitHub (Dec 5, 2020):

@lafriks
Hi,Will you fix this problem soon? I hope that the function of square merge is the same as GitHub, with the title as the commit message, and other information should not be automatically generated

@ffbh123456 commented on GitHub (Dec 5, 2020): @lafriks Hi,Will you fix this problem soon? I hope that the function of square merge is the same as GitHub, with the title as the commit message, and other information should not be automatically generated

GiteaMirror commented

2025-11-02 06:56:14 -06:00

@techknowlogick commented on GitHub (Dec 5, 2020):

@ZhouJiaZhi we are volunteers and don't get paid for our work on Gitea so we can't guarantee a timeline

@techknowlogick commented on GitHub (Dec 5, 2020): @ZhouJiaZhi we are volunteers and don't get paid for our work on Gitea so we can't guarantee a timeline

GiteaMirror commented

2025-11-02 06:56:14 -06:00

@jpraet commented on GitHub (Dec 8, 2020):

This is a duplicate of #12365. There's an open PR #13071 which would use the PR title and description as proposed commit message for a squash merge, instead of an aggregation of the individual commit messages. I think that's a good idea.

@jpraet commented on GitHub (Dec 8, 2020): This is a duplicate of #12365. There's an open PR #13071 which would use the PR title and description as proposed commit message for a squash merge, instead of an aggregation of the individual commit messages. I think that's a good idea.

Sign in to join this conversation.

Branches Tags

1 Participants

Notifications

Due Date

No due date set.

Dependencies

No dependencies set.

Reference: github-starred/gitea#6445