Closed yc283200832 closed 1 year ago
Hi @yc283200832 ,
This happens because the conflict is managed outside VS Code (Git itself) and so, the extension does not know how to update the bookmark position. Only operations made by VS Code itself are monitored.
I'm planning to review this concept in the future, but nothing official/ETA yet. If this really happen, this scenario would be supported.
Hope this helps
Environment/version
Steps to reproduce