Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Jump to bottom

Commit messages in chronological order for default squash and merge message #13661

Closed
2 of 6 tasks
jpraet opened this issue Nov 20, 2020 · 0 comments · Fixed by #13696
Closed
2 of 6 tasks

Commit messages in chronological order for default squash and merge message #13661

jpraet opened this issue Nov 20, 2020 · 0 comments · Fixed by #13696
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.

Comments

@jpraet
Copy link
Member

jpraet commented Nov 20, 2020

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

image

Desired:

image
jpraet added a commit to kszbcss/gitea that referenced this issue Nov 22, 2020
@jpraet
Use chronological commit order in default squash message (go-gitea#13661
5a297e4 
)
@6543 6543 added the type/proposal The new feature has not been accepted yet but needs to be discussed first. label Nov 24, 2020
@jpraet jpraet mentioned this issue Nov 24, 2020
Merged
techknowlogick pushed a commit that referenced this issue Nov 25, 2020
@jpraet
Use chronological commit order in default squash message (#13661) (#1…
03fa2ec 
…3696)
@go-gitea go-gitea locked and limited conversation to collaborators Jan 18, 2021
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Assignees
No one assigned
Labels
type/proposal The new feature has not been accepted yet but needs to be discussed first.
Projects
None yet
Milestone
No milestone
Development

Successfully merging a pull request may close this issue.

Use chronological commit order in default squash message kszbcss/gitea
2 participants
@jpraet @6543