Use chronological commit order in default squash message

[jpraet]

Fixes #13661

Note that the ticket also mentioned potentially removing the empty lines between commit messages. I haven't changed that for now because I'm not too sure about it. If you are squashing multiple commits, all with detailed multi-line commit messages, maybe the newlines are useful. Although one could also argue that the commit message details should maybe not be included in the squash message (only use the commit message titles)?

[silverwind]

PR looks fine.

As for newline squashing, I guess we could prefix the first line of a commit message with a * character like GitHub does, but with newlines squashed, except for the case when a multiline commit is followed by a single-line one, so for example:

* Remove fetch request from heatmap

Render heatmap data directly to HTML, eliminating one HTTP request on
frontpage and user profile. Also added min-height to the container so
the page content will no longer move after loading.

* rename and error display
* also log the js error
* add error handler
* remove useless inline style and hide divider on small screens
* Update routers/user/home.go
* Update routers/user/profile.go
* Remove fetch request from heatmap

Render heatmap data directly to HTML, eliminating one HTTP request on
frontpage and user profile. Also added min-height to the container so
the page content will no longer move after loading.

[lafriks]

Please update branch

[jpraet]

Please update branch

Could you clarify? Should I rebase on latest go-gitea:master?

[mrsdizzie]

There should be an update branch button at the bottom of the comments on this PR that will do it for you