Skip to content

feat(config): use succinct repo_url project remotes#1357

Merged
christso merged 1 commit into
mainfrom
feat/1354-repo-url
Jun 11, 2026
Merged

feat(config): use succinct repo_url project remotes#1357
christso merged 1 commit into
mainfrom
feat/1354-repo-url

Conversation

@christso

@christso christso commented Jun 11, 2026

Copy link
Copy Markdown
Collaborator

Summary

Follow-up to #1356 for issue #1354. The merged hard-break schema used GitHub owner/name repository fields and derived HTTPS clone URLs. Per follow-up design discussion, this switches Dashboard project/results config to a succinct Git remote schema:

projects:
  - id: agentv
    name: AgentV
    repo_url: https://github.com/EntityProcess/agentv.git
    path: /home/entity/projects/EntityProcess/agentv
    ref: main
    results:
      repo_url: git@github.com:EntityProcess/agentv-eval-results.git
      path: /home/entity/projects/EntityProcess/agentv-eval-results
      sync:
        auto_push: true

This uses repo_url for remote Git transport and path for local checkout paths at both levels.

Refs #1354; supersedes the repository owner/name shape merged in #1356.

Changes

  • Replace internal repository fields with camelCase repoUrl; YAML uses repo_url.
  • Project sync passes repoUrl directly to git clone, supporting HTTPS/SSH/file-style remotes.
  • Project results mapping reads results.repo_url and results.path.
  • Validation rejects removed fields with migration guidance:
    • projects[].source
    • projects[].repository
    • projects[].results.mode
    • projects[].results.repo
    • projects[].results.repository
    • projects[].results.local_path
    • projects[].results.auto_push
  • Dashboard docs show before/after migration examples using repo_url + path.

Red / Green UAT

  • Red: feat(config): hard-break dashboard project schema #1356 schema forced owner/name repository and then results.local_path, so SSH transport and succinct symmetric path naming were not represented.
  • Green: this branch accepts explicit Git remotes such as https://github.com/example/repo.git and git@github.com:example/repo.git; source and results local checkouts both use path.

Verification

  • bun run build
  • bun test packages/core/test/projects.test.ts packages/core/test/project-sync.test.ts packages/core/test/evaluation/validation/config-validator.test.ts apps/cli/test/commands/results/serve.test.ts
  • git diff --check
  • bun run lint
  • bun run typecheck
  • bun run test
    • core: 1847 pass
    • eval: 67 pass
    • phoenix-adapter: 22 pass
    • cli: 574 pass
    • dashboard: 83 pass

@cloudflare-workers-and-pages

cloudflare-workers-and-pages Bot commented Jun 11, 2026

Copy link
Copy Markdown

Deploying agentv with  Cloudflare Pages  Cloudflare Pages

Latest commit: a71eb30
Status: ✅  Deploy successful!
Preview URL: https://c3b9c030.agentv.pages.dev
Branch Preview URL: https://feat-1354-repo-url.agentv.pages.dev

View logs

@christso christso force-pushed the feat/1354-repo-url branch from c5cd36a to a71eb30 Compare June 11, 2026 05:37
@christso christso changed the title feat(config): use repo_url for dashboard project remotes feat(config): use succinct repo_url project remotes Jun 11, 2026
@christso christso merged commit 34b15e1 into main Jun 11, 2026
8 checks passed
@christso christso deleted the feat/1354-repo-url branch June 11, 2026 06:11
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant