Skip to content

GraphQL replication problem #7737

@jaynakus

Description

@jaynakus

On downstream js I found that if previous fork was not committed for unknown reasons. It assumes it as local change and doesn't allow new updates from server and just waits upstream to finalize it. However my setup is pull only. And app data not synchronized properly with server due to this issue. I couldn't come up with correct patch to fix it.

Metadata

Metadata

Assignees

No one assigned

    Projects

    No projects

    Milestone

    No milestone

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions