copier: Inline conflicts should use standard git markers
Actual Situation
I am using copier 8.3.0. When updating a rendered project that diverged from the template, inline markers are added to files with conflicts. These markers are custom to copier and therefore not recognized by git or my IDE.
Desired Situation
The marker should use the standard git notation and set the status of the destination git repository to “conflicts”. Similar to how https://github.com/cruft/cruft leaves the conflicting files after a failed git apply <patch>
.
Proposed solution
Would this not solve many problems elegantly? It would not only get rid of the need to use pre-commit
to prevent pushing conflicting files, as git
would not allow commiting the working tree in “conflicting files” state. Moreover, my IDE’s git integration would help me to solve conflicts visually (using, for example, the brilliant 3-way-merge tool of Jetbrains or VSCode).
About this issue
- Original URL
- State: closed
- Created 9 months ago
- Reactions: 1
- Comments: 18 (18 by maintainers)
Commits related to this issue
- feat: Mark files with conflict markers as unmerged Closes #1350 — committed to pawamoy/copier by pawamoy 8 months ago
- feat: Mark files with conflict markers as unmerged Closes #1350 — committed to pawamoy/copier by pawamoy 8 months ago
- feat: Mark files with conflict markers as unmerged Closes #1350 — committed to pawamoy/copier by pawamoy 8 months ago
- feat: Mark files with conflict markers as unmerged Closes #1350 — committed to pawamoy/copier by pawamoy 8 months ago
- feat: Mark files with conflict markers as unmerged Closes #1350 — committed to pawamoy/copier by pawamoy 8 months ago
- feat: Conflicts on updates now appear as git merge conflicts, also on VSCode Closes #1350 — committed to pawamoy/copier by pawamoy 8 months ago
Well, it looks like this became actionable!
It’s working just fine on my end.