<!--IssueSummary start--> <details> <summary> Everyone can contribute. [Help move this issue forward](https://handbook.gitlab.com/handbook/marketing/developer-relations/contributor-success/community-contributors-workflows/#contributor-links) while earning points, leveling up and collecting rewards. </summary> - [Close this issue](https://contributors.gitlab.com/manage-issue?action=close&projectId=278964&issueIid=576259) </details> <!--IssueSummary end--> # Steps to reproduce 1. create a Wiki page with a Draw.io diagram in via offline editor, e.g. ```markdown  ``` 2. upload the page using `git push` 3. edit the diagram using the Web editor's Draw.io integration # Actual behavior The Diagram creates a new file at `uploads/2676202326d87cfc10aa26758d9db493/CloudStoragesDiagram.drawio.svg` and modifies the Wiki page accordingly. # Expected behavior The Diagram is modified in place, the file location is preserved, and the wiki page remains unmodified. # Impact We really love the Draw.io integration of Gitlab's Wiki, but this issue causing unneccessary friction and heat in our team. Users insisting in maintaining the Wiki via git are highly annoyed by the web users destroying their carefully crafted directory structure gets destroyed. This arguing is disasterious for team dynamics and prevents Gitlab adoption. As long as Gitlab is disputed and spoils team dynamics, our intendet move to Gitlab Premium is blocked.