Repository navigation
[bug]: Bidirectional GitHub issue sync rewrites issue bodies on GitHub at sync time (Mermaid flattened, lists reformatted, images re-hosted) #10171
Description
Environment
Plane Commercial, self-hosted (Docker, installed with prime-cli), v3.3.3 then v4.0.1. GitHub integration with Project Issue Sync set to Bidirectional, issues synced through the plane label.
What happens
When an issue is synced to Plane, the GitHub App rewrites the issue's body on GitHub within a few minutes, although nobody edited the work item in Plane. The edit is attributed to the app in the issue's edit history. On one repository, 76 issue bodies were rewritten this way:
- Mermaid code blocks are flattened: the fenced block loses its line breaks (
flowchart LR A([MO load]) --> B{…} B -- no --> …), a strayLoadingline is appended, and GitHub no longer renders the diagram. - Images are re-hosted:
becomes. The alt text is lost and the URL is private to the Plane instance, so the image is broken for every GitHub reader (see GitHub<img>tags losealt, replaced with auth-gated silo URLs #9073). - Lists are reformatted:
-becomes*,1.becomes1., a blank line is added after every item, nested lists are re-indented.
Steps to reproduce
- Set a project's Issue Sync to Bidirectional.
- Create a GitHub issue whose body has a Mermaid block, a nested list and a
user-attachmentsimage. - Add the
planelabel. - Within a few minutes, the issue's edit history shows an edit by the GitHub App with the changes above.
With Issue Sync set to Unidirectional, the same issue is not rewritten (checked: no edit after 5 minutes).
Expected
Syncing an issue into Plane never writes to the GitHub issue. A Plane → GitHub push happens only when someone edits the work item in Plane, and only for the fields they changed; it never sends back a re-serialised version of content that came from GitHub unchanged.
Related
#9073 (images), #9077 (closed as fixed on Plane Cloud; still reproducible on self-hosted v4.0.1), #9071, #9072.
Activity