Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

merge_tools: allow setting conflict marker style per-tool #4951

Merged
merged 1 commit into from
Nov 26, 2024

Conversation

scott2000
Copy link
Contributor

Follow-up to #4897.

Checklist

If applicable:

  • I have updated CHANGELOG.md
  • I have updated the documentation (README.md, docs/, demos/)
  • I have updated the config schema (cli/src/config-schema.json)
  • I have added tests to cover my changes

@scott2000 scott2000 force-pushed the merge-tool-conflict-marker-style branch 7 times, most recently from a587a02 to 00379a2 Compare November 23, 2024 15:00
@scott2000 scott2000 marked this pull request as ready for review November 23, 2024 15:02
@scott2000 scott2000 force-pushed the merge-tool-conflict-marker-style branch from 00379a2 to 2279d2f Compare November 23, 2024 21:27
@scott2000 scott2000 force-pushed the merge-tool-conflict-marker-style branch 2 times, most recently from 2a8c285 to 896e6f9 Compare November 25, 2024 17:16
docs/config.md Outdated Show resolved Hide resolved
I left the "merge-tool-edits-conflict-markers" option unchanged,
since removing it would likely break some existing configurations. It
also seems like it could be useful to have a merge tool use the default
conflict markers instead of requiring the conflict marker style to
always be set for the merge tool (e.g. if a merge tool allows the user
to manually edit the conflicts).
@scott2000 scott2000 force-pushed the merge-tool-conflict-marker-style branch from 896e6f9 to 1e547e6 Compare November 26, 2024 14:38
@scott2000 scott2000 merged commit 7f57866 into jj-vcs:main Nov 26, 2024
18 checks passed
@scott2000 scott2000 deleted the merge-tool-conflict-marker-style branch November 26, 2024 15:08
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.

3 participants