Revetly
Manual 0.8.0

Move a backlog to GitHub

Move the ready items of a repo-backed backlog onto GitHub Issues without losing their ids, their parents or their citations. The token needs Issues read and write, the labels the target types map to must already exist, and each old file ends flipped to discarded with a same_as claim.

Before you start

Configuration page

Command line

  1. Read the plan, with [backend] pbi still set to repo: 

    revetly migrate-backlog --to github --project <PROJECT> --dry-run

    Replace <PROJECT> with the key of the project whose backlog you move, and add one --status per status to move in place of ready.

    project '<PROJECT>' -> github
<COUNT> item(s) in create order, <MUTATIONS> mutation(s)

  2. Apply the plan, still with [backend] pbi set to repo: 

    revetly migrate-backlog --to github --project <PROJECT> --apply --decision <DEC_ID>

    Replace <DEC_ID> with the id of the recorded decision.

    created <N>, adopted <N>, linked <N>, status set <N>, files flipped <N>, steps skipped <N>

  3. In revetly.toml at the project root, keep pm enabled and switch the store only after the records commit:

    # revetly.toml
[connectors]
enabled = ["pm", "docs", "conversations", "deliveries", "github"]

[backend]
pbi = "github"

    Revetly replaces the enabled list rather than merging into it, so it restates every source already read, and pm keeps reading the old files an old id answers from.

  4. Read that no work item is left live in two stores:

    revetly doctor --offline

    [PASS] duplicate stores  no work item is live in two stores

Next steps