Skip to content

conflict support 5 - add merge conflict-state minimap#6

Merged
polyphilz merged 1 commit into
mainfrom
polyphilz/3-pane-3.5
Apr 27, 2026
Merged

conflict support 5 - add merge conflict-state minimap#6
polyphilz merged 1 commit into
mainfrom
polyphilz/3-pane-3.5

Conversation

@polyphilz
Copy link
Copy Markdown
Owner

No description provided.

Copy link
Copy Markdown

@chatgpt-codex-connector chatgpt-codex-connector Bot left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: fee7222193

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

  • Open a pull request for review
  • Mark a draft as ready
  • Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

Comment thread lua/glance/config.lua
accept_both_theirs_then_ours = true,
ignore_ours = true,
ignore_theirs = true,
keep_base = true,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P1 Badge Accept legacy ignore_ merge key names*

Removing ignore_ours and ignore_theirs from the allowed merge keymap set will now make setup() fail for existing configs that still include those previously supported keys, because validate_known_keys treats them as unknown and errors out. This creates an upgrade-time startup break for users who copied prior defaults, so these keys should be accepted as backward-compatible aliases (or migrated to keep_base) before validation.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Not necessary

Comment on lines +9 to +10
MERGE_UNRESOLVED = 5,
MERGE_HANDLED = 6,
Copy link
Copy Markdown

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

P2 Badge Give unresolved conflicts precedence in minimap states

MERGE_UNRESOLVED is assigned a lower numeric state than MERGE_HANDLED, but downsample() picks the highest state value when multiple lines map to one minimap pixel. On long files where unresolved and handled conflicts collapse into the same pixel, unresolved conflicts will be painted as handled, which hides remaining unresolved work in the minimap. Assign unresolved a higher priority than handled (or use explicit priority ordering) to keep unresolved conflicts visible.

Useful? React with 👍 / 👎.

Copy link
Copy Markdown
Owner Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Resolved in polyphilz/3-pane-7

@polyphilz polyphilz force-pushed the polyphilz/3-pane-3.25 branch from 0986ca0 to 5875fa0 Compare April 27, 2026 00:36
@polyphilz polyphilz changed the base branch from polyphilz/3-pane-3.25 to main April 27, 2026 00:44
@polyphilz polyphilz changed the title add merge conflict-state minimap conflict support 5 - add merge conflict-state minimap Apr 27, 2026
@polyphilz polyphilz force-pushed the polyphilz/3-pane-3.5 branch from fee7222 to dc07749 Compare April 27, 2026 00:45
@polyphilz polyphilz merged commit 11caee5 into main Apr 27, 2026
3 checks passed
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