Skip to content

fix(leaderboard): use upstream schema for fork PR validation#335

Open
kami619 wants to merge 1 commit intoambient-code:mainfrom
kami619:bugfix/leaderboard-use-upstream-schema
Open

fix(leaderboard): use upstream schema for fork PR validation#335
kami619 wants to merge 1 commit intoambient-code:mainfrom
kami619:bugfix/leaderboard-use-upstream-schema

Conversation

@kami619
Copy link
Collaborator

@kami619 kami619 commented Mar 5, 2026

When a user submits a leaderboard entry from a fork that hasn't been synced with upstream, the workflow was using the fork's outdated schema for validation. This caused valid submissions to fail with errors like "attributes_total: 25 was expected" even though PR #312 had already fixed the schema to allow 10-25 attributes.

This fix changes the workflow to:

  1. Checkout upstream main for validation tools and schema
  2. Fetch only the submission file from the PR branch
  3. Validate using upstream's agentready installation

This ensures validation always uses the latest schema while still validating the actual submitted file from the PR.

Fixes the validation failure on PR #332.
See: #312

When a user submits a leaderboard entry from a fork that hasn't been synced
with upstream, the workflow was using the fork's outdated schema for
validation. This caused valid submissions to fail with errors like
"attributes_total: 25 was expected" even though PR ambient-code#312 had already fixed
the schema to allow 10-25 attributes.

This fix changes the workflow to:
1. Checkout upstream main for validation tools and schema
2. Fetch only the submission file from the PR branch
3. Validate using upstream's agentready installation

This ensures validation always uses the latest schema while still validating
the actual submitted file from the PR.

Fixes the validation failure on PR ambient-code#332.
See: ambient-code#312

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
@github-actions
Copy link
Contributor

github-actions bot commented Mar 5, 2026

📈 Test Coverage Report

Branch Coverage
This PR 66.8%
Main 66.8%
Diff ✅ +0%

Coverage calculated from unit tests only

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