Hacktoberfest 2026:维护者为十月标记出来的 issue,仍然开放、适合新手。 浏览 Hacktoberfest issue

Write documentation for migrating workflow code

已关闭
#903 0 条评论 0 个 reaction 已指派 1 人 在 GitHub 查看

维护者通常 1 天内回复

@PiusKariuki 已经在做这个了。

开始于 2026年10月7日。

  • #904 来自 @PiusKariuki —— 已合并

评估

这个 Issue 还没有评估数据。

描述

P1

Objective

Document how a user can migrate a workflow from one OpenFn project to another by copying its YAML on Lightning.

Scope

  • In scope: Copying workflow YAML between projects via the Lightning UI (export from source, paste into target).

Required Sections

  1. Overview — one paragraph: what YAML migration is, when to use it, what it does not carry over (credentials, run history, webhook URLs).
  2. Prerequisites
    • Access to both source and target projects
    • Matching adaptor versions available on the target instance.
  3. Steps
    • Open the source workflow and export/copy its YAML
    • Open the target project and create a new workflow (or open the workflow editor)
    • Paste the YAML, review the diff, confirm deploy
    • Screenshots for each step
  4. What gets migrated vs. what doesn't
  • Table: jobs, triggers, edges, workflow structure (migrated) vs. credentials, run history, webhook URLs, collaborators (not migrated).
  1. Reconnecting credentials on the target
  • Credentials are referenced by name/ID; show how to recreate or remap them in the target project
  1. Verification checklist
    • Workflow appears in target, adaptor versions resolved, trigger reconfigured, one test run completes
  2. Common pitfalls
    • Adaptor version mismatch
    • Stale credential references

Acceptance Criteria

  • UI steps documented with screenshots
  • Explicit list of what does and does not transfer with the YAML
  • Credential-remapping steps included
  • Verification checklist a user can run through in under 5 minutes
  • Common pitfalls section with at least the 2 cases above
  • Linked from the Workflows index page
主要语言
JavaScript
星标
25
派生
22
平均合并
1 天 3 小时
30 天内合并 PR
56

环境准备

  • 没有 Dockerfile 或 Docker Compose 文件
  • 有 Pull Request 模板
  • 没有贡献指南

从这里开始

  1. 先读完整个 Issue,再读项目的贡献指南。
  2. 在 Issue 下留言说明你要接手 —— 这能避免两个人做同样的事。
  3. Fork 仓库,在一个分支上完成修改。
  4. 提交 Pull Request,并在描述里引用这个 Issue 编号。

OpenFn/docs 的其他 Issue

查看 OpenFn/docs 的全部 Issue

相似的 Issue

更多 JavaScript Issue

把新 issue 发到你的邮箱

精选适合新手参与的 GitHub issue 摘要。