Stefan HallerandClaude Opus 5 9183269ee8 Write a reflog message when moving branch refs ...

Branches that lazygit forwards to their upstream move by a direct ref
write, so no git command turns up in their reflog to explain it. Until
now the entry had no message either, leaving `git reflog <branch>` with
nothing but a blank line about it. Name lazygit and what it did, so that
a branch which moved on its own can be traced.

Co-Authored-By: Claude Opus 5 (1M context) <noreply@anthropic.com>

2026-09-27 11:00:36 +02:00

..

direnv

Offer direnv .envrc approval from inside lazygit

2026-06-04 09:05:01 +02:00

git_commands

Write a reflog message when moving branch refs

2026-09-27 11:00:36 +02:00

git_config

Pin the cached git config's commands to the repo directory

2026-07-20 17:07:39 +02:00

hosting_service

Optimize regex compilations

2026-05-10 15:28:14 +02:00

models

Dim the divergence of a branch whose upstream was rewritten

2026-09-27 11:00:36 +02:00

oscommands

Keep coverage errors out of the output of the pipeline tests

2026-09-26 12:10:37 +02:00

patch

Preallocate arrays where the new linter version would warn about it

2026-08-16 16:35:11 +02:00

testdata

…

git_cmd_obj_builder_test.go

Tell git where the repo is when it can't find it itself

2026-08-08 11:15:01 +02:00

git_cmd_obj_builder.go

Tell git where the repo is when it can't find it itself

2026-08-08 11:15:01 +02:00

git_cmd_obj_runner_test.go

Back off exponentially between lock-error retries

2026-07-15 10:08:44 +02:00

git_cmd_obj_runner.go

Back off exponentially between lock-error retries

2026-07-15 10:08:44 +02:00

git.go

Dim the divergence of a branch whose upstream was rewritten

2026-09-27 11:00:36 +02:00