Skip to content

chore(lazygit): use git.pagers (array) instead of legacy git.paging#8

Open
ShortArrow wants to merge 1 commit into
mainfrom
chore/lazygit-pagers-modern-form
Open

chore(lazygit): use git.pagers (array) instead of legacy git.paging#8
ShortArrow wants to merge 1 commit into
mainfrom
chore/lazygit-pagers-modern-form

Conversation

@ShortArrow

@ShortArrow ShortArrow commented Jun 9, 2026

Copy link
Copy Markdown
Owner

Summary

Rewrite git.paging: (singular object) as git.pagers: (one-element array) in lazygit/config.yml.

Why

Lazygit replaced the singular paging object with the plural pagers array in v0.55.0 — the array form lets users cycle through multiple pager configs. The old key still works because migratePagers in pkg/config/app_config.go silently rewrites it at load time, but explicitly using the modern shape keeps the file aligned with the current schema and stops depending on the migration shim.

Behavior is identical: diff-so-fancy continues to be used with colorArg: always.

Test plan

  • Verified via lazygit source (deepwiki): git.paging is migrated to git.pagers automatically since v0.55.0 — both forms produce the same runtime behavior.
  • Local lazygit (0.62.2) starts cleanly with the new config and diff-so-fancy rendering remains intact on a commit diff view.

Lazygit replaced the singular `git.paging:` object with a plural
`git.pagers:` array in v0.55.0 (the array form lets users cycle
through multiple pager configs). The old key still works via a
built-in migration handler (migratePagers in pkg/config/app_config.go),
so this is a no-op for behavior — but rewriting the config in the
modern shape avoids relying on the compatibility shim and keeps the
file aligned with the current schema.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant