-
Notifications
You must be signed in to change notification settings - Fork 238
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.
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
Commit sotring is unstable #209
Milestone
Comments
ikedam
added a commit
to ikedam/git-chglog
that referenced
this issue
Sep 17, 2022
Use `sort.SliceStable` instead of `sort.Slice` to sort commits. Closes git-chglog#209
2 tasks
ikedam
added a commit
to ikedam/git-chglog
that referenced
this issue
Jan 24, 2023
Use `sort.SliceStable` instead of `sort.Slice` to sort commits. Closes git-chglog#209
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Expected Behavior
The order of log entries are always same for any configurations if
options.commits.sort_by
is not changed.Actual Behavior
The order of log entries differs for different configurations, even if
options.commits.sort_by
is not changed.This means the sorting for commit is performed with an unstable sort algorithm.
Steps to Reproduce (including precondition)
Create a changelog for
[email protected]
:Change the configuration:
Create a changelog for
[email protected]
with the new configuration:Compare them:
I found this behavior when I updated the git-chglog configuration for my repository to pick new commits. I expected new logs, but didn't expected changing the order of logs.
Screenshot on This Problem (if possible)
N/A
Your Environment
The text was updated successfully, but these errors were encountered: