Skip to content

Conversation

jserv
Copy link
Contributor

@jserv jserv commented Mar 3, 2025

This commit introduces a pre-commit hook that checks for merge conflict markers (e.g. "<<<<<<<", "=======", ">>>>>>>") in staged changes. If any are detected, the hook warns the user and aborts the commit, ensuring that unresolved conflict markers are not inadvertently committed.

Reference:
https://blog.meain.io/2019/making-sure-you-wont-commit-conflict-markers/

Change-Id: Ia3b058298f9e38227bdbd7a3634ed9b0b855e374

This commit introduces a pre-commit hook that checks for merge conflict
markers (e.g. "<<<<<<<", "=======", ">>>>>>>") in staged changes. If any
are detected, the hook warns the user and aborts the commit, ensuring
that unresolved conflict markers are not inadvertently committed.

Reference:
  https://blog.meain.io/2019/making-sure-you-wont-commit-conflict-markers/

Change-Id: Ia3b058298f9e38227bdbd7a3634ed9b0b855e374
@jserv jserv merged commit e151924 into master Mar 3, 2025
4 checks passed
@jserv jserv deleted the prevent-merge-conflicts branch March 3, 2025 18:02
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