Skip to content

Phase 1: Foundation — Repo transfer, branding, CI updates #119

@ajianaz

Description

@ajianaz

Phase 1: Foundation (Week 1)

Transfer repo to codecoradev org, update all branding references, ensure CI works.

Tasks

1.1 Repo Transfer

  • Verify codecoradev org exists + Sibung has admin access
  • Transfer ajianaz/cora-clicodecoradev/cora-cli via GitHub Settings → Transfer ownership
  • Verify: gh api /repos/codecoradev/cora-cli
  • Update local remote: git remote set-url origin https://github.com/codecoradev/cora-cli.git
  • Verify CI triggers on new repo (open a test push)

1.2 Cargo.toml + README URL Updates

  • Cargo.toml: repository = "https://github.com/codecoradev/cora-cli"
  • README.md: all ajianaz/cora-cli links → codecoradev/cora-cli
  • CHANGELOG.md: compare links update (all URLs)
  • Website files (website/src/**/*.svelte): any hardcoded repo URLs

1.3 CI Workflow Updates

  • .github/workflows/ci.yml: badge URLs (if any in README)
  • .github/workflows/release.yml: no hardcoded org refs needed (uses github.repository)
  • .github/workflows/cora-review.yml: verify uses relative action ref ./.github/actions/cora-review
  • .github/workflows/deploy-website.yml: CF Pages project name stays cora
  • Verify: push to develop → CI passes on new repo

1.4 Cora Review Action Refs

  • .github/actions/cora-review/action.yml: download URL uses gh release download which auto-resolves to current repo — should work
  • Test: open test PR on new repo → cora review job downloads binary and runs
  • If other repos use this action: update their .github/actions/cora-review submodule ref

1.5 Skills & Memory Update

  • CTO skill (cora-cli SKILL.md): update repo URL to codecoradev/cora-cli
  • Persistent memory: update all ajianaz/cora-cli references
  • Any other agent configs referencing old repo URL

Acceptance Criteria

  • codecoradev/cora-cli repo accessible at https://github.com/codecoradev/cora-cli
  • CI passes on new repo (push to develop → 8/8 green)
  • Binary download works from new repo releases
  • cargo search cora-cli still resolves (crates.io unaffected)
  • All internal docs/skills/memory updated

Depends On

  • None (first phase)

Blocks

  • Phase 2 (website deploy to codecora.dev needs repo under codecoradev)
  • Phase 3 (GitHub App backend links to codecoradev/cora-cli)

Epic

Metadata

Metadata

Assignees

No one assigned

    Labels

    migration:brandBranding, copy, README, messagingmigration:infraRepo transfer, DNS, CF Pages, org setupmigration:v2CodeCora V2 Migration — all tracking issuesphase:week1W1 Foundation

    Type

    No type
    No fields configured for issues without a type.

    Projects

    No projects

    Relationships

    None yet

    Development

    No branches or pull requests

    Issue actions