sublimehq / sublime_merge

Issue tracker for Sublime Merge
https://www.sublimemerge.com
272 stars 14 forks source link

Bug when selecting multiple commits #1941

Open elvanderb opened 2 months ago

elvanderb commented 2 months ago

Version info

Description

When selecting multiple non contiguous commits (with ctrl+left click for example), all the commits between the min and the max are considered (except the oldest selected) when exporting a patch or exploring the commit change logs in the right panel.

Steps to reproduce

Steps to reproduce the behavior:

  1. Open repository ...
  2. select two non adjacent commits (by keeping ctrl pressed)
  3. see that commits between those two commits are printed in the right panel and included in the patch generated with the right-click -> Save Patch menu
  4. see that the older commit is not considered

Expected behavior

Every selected commits should be considered and only them

Debug Information The Sublime Merge debug information can be used to narrow down the cause of an issue. It can be collected with the following steps:

=== App Version Information ===
Build: 2096

=== Git Version Information ===
Using Git: git (system)
git version 2.39.2
PATH: [REDACTED]

=== Git Status Information ===
?? Patch.patch

=== Our Status Information ===
?? Patch.patch

=== Git Config Information ===
branch[REDACTED]=[REDACTED]
branch[REDACTED]=[REDACTED]
branch[REDACTED]=[REDACTED]
branch[REDACTED]=[REDACTED]
branch[REDACTED]=[REDACTED]
branch[REDACTED]=[REDACTED]
core.bare=false
core.filemode=true
core.hookspath=tools/[REDACTED]/githooks/
core.logallrefupdates=true
core.repositoryformatversion=0
pull.rebase=false
remote.origin.fetch=+refs/heads/*:refs/remotes/origin/*
remote.origin.url=[REDACTED]
user.email=[REDACTED]
user.name=[REDACTED]

=== Our Config Information ===
Git Config Path Information
Using config path: /etc/gitconfig
Using config path: /home/[REDACTED]/.config/git/config
Using config path: /home/[REDACTED]/.gitconfig
Using config path: /[REDACTED]/.git/config

Our config output is identical to the Git config output

=== Git Attributes Information ===
git check_attr --all output

=== Our Modified Files Newline Normalisation and EOL Information ===

=== Our Modified Files Flag Information ===
Ignoring symlinks: 0

Screenshots

image image image

In the first screenshot we should only see "d" and "a" commits but we see "d", "c", "b" and not "a"

elvanderb commented 1 month ago

It seems that #1609 describes the same issue.