Skip to content

GitHub @mentions corrupted to [From GitHub: user](url) on sync #9071

Open

Description

@aspiers

Affected: Plane Cloud, official GitHub integration. See also: meta-issue on destructive overwrite (issue 01).

Symptom

GitHub markdown @username written in an issue or comment body, after a GH→Plane import + Plane→GH round-trip, comes back as [From GitHub: username](https://github.com/username).

stage content
GitHub input @someuser
Plane stored HTML <a href="https://github.com/someuser" rel="noopener noreferrer">From GitHub: someuser</a>
GH after Plane→GH push [From GitHub: someuser](https://github.com/someuser)

The From GitHub: <handle> text is injected at GH→Plane import time by the closed makeplane/silo-commercial image. The Plane→GH markdown serialisation then faithfully emits it.

Impact

  • Loses GitHub-native mention semantics: no notification to the mentioned user, no avatar in GH rendering, no auto-link styling.
  • Visually ugly: @user becomes From GitHub: user everywhere.
  • Words that look like mentions but aren't valid users still get linked to broken URLs. e.g. the literal text @mentions becomes [From GitHub: mentions](https://github.com/mentions) — a 404.

Ask

Preserve @user mentions as bare @user text across the round-trip. Do not invent [From GitHub: user](url) link forms.

If conversion to a link is unavoidable, validate the handle against GitHub's user API and skip the rewrite for non-existent users rather than producing a broken link.

Reproduction

  1. Connect a GitHub repo to a Plane workspace via the official GitHub integration. Set sync to bidirectional.
  2. Create a GitHub issue with body cc @someuser. Apply the Plane label.
  3. Within seconds the Plane work item appears with description_html already containing <a href="https://github.com/someuser">From GitHub: someuser</a>.
  4. To exercise the destructive Plane→GH push, follow the trigger recipe in meta-issue 01.

Activity

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Metadata

Metadata

Assignees

No one assigned

    Labels

    No labels
    No labels

    Type

    No type

    Fields

    No fields configured for issues without a type.

    Projects

    No projects

      Milestone

      No milestone

      Relationships

      None yet

      Development

      No branches or pull requests

      Issue actions