Commit messages in chronological order for default squash and merge message

[jpraet]

• Gitea version (or commit ref): 1.12.6
• Operating system: docker
• Database (use [x]):
  • PostgreSQL
  • MySQL
  • MSSQL
  • SQLite
• Can you reproduce the bug at https://try.gitea.io:
  • Yes (https://try.gitea.io/jpraet/test/pulls/3)
  • No

Description

The default generated commit message for squash and merge places the commit messages in reverse chronological order. Wouldn't it make more sense to put these in chronological order, to keep the order of the steps that were done to implement the change? Also, there is a blank line in between each commit message which I don't think is really necessary?

Screenshots

Desired: