OpenFn / OpenFn/kit

Sync stability

Open
#1,480 0 comments 0 reactions 1 assignee View on GitHub

@josephjclark is already working on this.

Since Jul 14, 2026.

Dominant language
TypeScript
Stars
21
Forks
23
Avg merge
1d 22h
Merged PRs (30d)
17

Description

This is an epic to close out a bunch of sync issues. Workflow aliases is a stretch goal, the rest are critical.

After this is complete, the status of sync I think is:

  • We should be able to use v2 sync by default in all new GH syncs
  • v2 sync CLI should be the standard for all new deployments
  • Divergence warnings can still be a bit flaky (but v1 has no divergence warning at all!)
  • Conflict resolution is super hard (v1 just overwrites so silently ignores conflicts and drops work)

Those last two points are to be tackled later. Divergence warnings were always part of the v2 plan and need fixing, but conflict resolution was always out of scope

Contributor guide

No contributing guide indexed for this repository

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

Assessment

This issue has not been assessed yet.

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.