Commit Graph
6 Commits
Author SHA1 Message Date
Stefan HallerandClaude Opus 5.5 af0e6ab7f2 Make "go to bottom" in a divergence view stop at the last remote commit
The divergence view shows the remote commits in a section above the
local ones. Pressing '>' now goes to the beginning of the remote section
before it goes on to the bottom of the local one.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 14:08:51 +01:00
Stefan HallerandClaude Opus 5.5 280c67ff98 Make "go to bottom" stop at the bad, current and good commits of a bisect
During a bisect, the commits panel shows the commits known to be bad at
the top, the known good ones at the bottom, and the ones that the bisect
hasn't ruled out yet between them. Pressing '>' now stops at the
bottommost bad commit, then at the commit to test, and then at the
topmost good commit.

It doesn't stop at each commit marked good. The commits between two of
them are all good, and they don't form a section of their own.

During a bisect, it also doesn't stop at the beginnings of the other
sections, such as the beginning of a branch. The commits panel doesn't
color the commits by whether they are merged while bisecting, so these
would look like arbitrary commits.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 14:08:51 +01:00
Stefan HallerandClaude Opus 5.5 462a168d87 Make "go to bottom" stop at the beginning of each branch of a stack
In a stack of branches, pressing '>' in the commits panel went to the
beginning of the bottommost branch right away. Make it go to the
beginning of the branch that the selection is in first, and then to the
beginning of each branch below it. During a rebase, the update-ref todos
separate the branches among the todos, so stop above each of them too.

The branches of the stack are the ones that the commits list marks, and
that pushing and pulling a stack include.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 12:46:15 +01:00
Stefan HallerandClaude Opus 5.5 33f52279c4 Make "go to bottom" in the commits panel stop at the first todo
During a rebase, cherry-pick or revert, the todos are a section of their
own at the top of the commits panel. Pressing '>' now goes to the first
of them, the bottommost one, before it goes on to the beginning of the
branch.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 12:42:48 +01:00
Stefan HallerandClaude Opus 5.5 7426d7f934 Don't let "go to bottom" in the commits panel go up
The command went to the commit above the first merged one whenever the
commit below the selection wasn't merged. It did this even if the
selection was below that commit already.

Collect the places where the command can stop, and go to the closest one
below the selection, or to the bottom if there is none. This also makes
it easy to add more places to stop at.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 12:41:57 +01:00
Stefan HallerandClaude Opus 5.5 97aeaf77a5 Unify the "go to bottom" logic of the two commit list contexts
The local commits and the sub-commits contexts had identical copies of
it. We are going to make it smarter, so make sure the copies don't
drift apart.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
2026-11-08 12:40:28 +01:00