You signed in with another tab or window. Reload to refresh your session.You signed out in another tab or window. Reload to refresh your session.You switched accounts on another tab or window. Reload to refresh your session.Dismiss alert
{{ message }}
Repository navigation
Soft-wrapped paragraphs converted to hard <p> breaks on sync #9076
Affected: Plane Cloud, official GitHub integration. See also: meta-issue on destructive overwrite (issue 01).
Symptom
Issue or comment bodies whose paragraphs are soft-wrapped at ~80 characters with literal newlines have those internal newlines turned into hard paragraph breaks after a sync round-trip.
Input: body wraps at ~80 characters with literal \n inside paragraphs (a common convention for human-written markdown).
Pushed back to GH markdown: internal newlines become hard <p> breaks, turning soft-wrapped prose into a sequence of single-line paragraphs that read very differently from the original.
Impact
Lower severity than the other patterns — the text content is preserved, just reformatted. But the reformatting is unwanted and visible to anyone using deliberate soft wrapping.
Ask
Treat single \n inside a paragraph as soft-wrap (or non-significant whitespace), matching GitHub-Flavoured Markdown's default rendering. Only treat blank lines (\n\n) as paragraph separators.
Reproduction
Connect a GitHub repo to a Plane workspace via the official GitHub integration. Set sync to bidirectional.
Create a GitHub issue whose body contains a single paragraph wrapped over multiple lines (no blank lines inside the paragraph). Apply the Plane label.
To exercise the destructive Plane→GH push, follow the trigger recipe in meta-issue 01.
Activity