Skip to content

Migration from GitHub Projects

Kiket offers deeper workflow automation than GitHub Projects while staying Git-native. Follow these steps to migrate.

1. Inventory Current Setup

  • Export project boards (CSV) to capture columns, statuses, and custom fields.
  • List workflows or automations handled by GitHub Actions or third-party apps.
  • Identify repositories contributing issues.

2. Prepare Kiket Configuration

  • Create .kiket/workflows/ that reflect the states used in GitHub Projects.
  • Translate project views into .kiket/boards/ YAML with columns and filters.
  • If you use iteration or roadmap views, replicate them with swimlanes or timeline boards.

3. Sync Repositories

  • Connect GitHub via Kiket Organization settings.
  • Create a project and select the repositories you want to manage.
  • Run the initial sync to pull workflows and boards.

4. Import Issues

  • Use the CLI: kiket migrate github-project --project <project-id> --target <kiket-project>.
  • Map GitHub fields to Kiket fields (priority, labels, assignees) using the CLI prompts.
  • Attach linked pull requests automatically using repository metadata.

5. Replace Automations

  • Convert GitHub Actions workflows to KiketScript actions or extensions.
  • Set up webhooks to trigger deployments, notifications, or analytics updates.

6. Train the Team

  • Demonstrate how workflow changes happen via Git.
  • Review board provenance badges that link back to the defining repository file.
  • Share the command palette shortcuts (Cmd/Ctrl + K) for quick navigation.

7. Monitor & Improve

  • Use analytics dashboards to track throughput compared to your legacy process.
  • Iterate on workflow YAML as teams learn what works best.

Migrating ensures your project management stays tied to code while unlocking automation across the entire software lifecycle.