github-starred/gitea
2
0
Fork 0
mirror of https://github.com/go-gitea/gitea.git synced 2026-03-24 23:46:30 -05:00
Code Issues 2.6k Packages Projects Releases 100 Wiki Activity

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

New Issue
Closed
opened 2025-11-02 06:53:41 -06:00 by GiteaMirror · 0 comments
GiteaMirror commented 2025-11-02 06:53:41 -06:00
Owner
Copy Link

Originally created by @jpraet on GitHub (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

Originally created by @jpraet on GitHub (Nov 20, 2020). - Gitea version (or commit ref): 1.12.6 - Operating system: docker - Database (use `[x]`): - [x] PostgreSQL - [ ] MySQL - [ ] MSSQL - [ ] SQLite - Can you reproduce the bug at https://try.gitea.io: - [x] 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 ![image](https://user-images.githubusercontent.com/2212615/99845119-6b388900-2b74-11eb-9b10-76719b891b73.png) Desired: ![image](https://user-images.githubusercontent.com/2212615/99845177-84413a00-2b74-11eb-8354-8f171c6ebbe0.png)
GiteaMirror added the type/proposal label 2025-11-02 06:53:41 -06:00
Sign in to join this conversation.
No Branch/Tag Specified
Branches Tags
Labels
Clear labels
$20
$250
$50
$500
backport/done
💎 Bounty
docs-update-needed
good first issue
hacktoberfest
issue/bounty
issue/confirmed
issue/critical
issue/duplicate
issue/needs-feedback
issue/not-a-bug
issue/regression
issue/stale
issue/workaround
lgtm/need 2
modifies/api
modifies/translation
outdated/backport/v1.18
outdated/theme/markdown
outdated/theme/timetracker
performance/bigrepo
performance/cpu
performance/memory
performance/speed
pr/breaking
proposal/accepted
proposal/rejected
pr/wip
pull-request
Mirrored from GitHub Pull Request
 reviewed/wontfix
💰 Rewarded
skip-changelog
status/blocked
topic/accessibility
topic/api
topic/authentication
topic/build
topic/code-linting
topic/commit-signing
topic/content-rendering
topic/deployment
topic/distribution
topic/federation
topic/gitea-actions
topic/issues
topic/lfs
topic/mobile
topic/moderation
topic/packages
topic/pr
topic/projects
topic/repo
topic/repo-migration
topic/security
topic/theme
topic/ui
topic/ui-interaction
topic/ux
topic/webhooks
topic/wiki
type/bug
type/deprecation
type/docs
type/enhancement
type/feature
type/miscellaneous
type/proposal
type/question
type/refactoring
type/summary
type/testing
type/upstream
No Label type/proposal
Milestone
No items
No Milestone
Projects
Clear projects
No project
Assignees
Clear assignees
GiteaMirror ninjasurge
No Assignees
1 Participants
Notifications
Due Date
No due date set.
Dependencies

No dependencies set.

Reference: github-starred/gitea#6366
Delete Branch "%!s()"

Deleting a branch is permanent. Although the deleted branch may continue to exist for a short time before it actually gets removed, it CANNOT be undone in most cases. Continue?