mohitagw15856 4209963cff Leaderboard workflow: open a PR instead of pushing to protected main (#45) ...

The eval run worked (12 scored runs) but the final step failed: it pushed
evals/results.json directly to main, which the branch ruleset blocks
("Changes must be made through a pull request").

- eval-leaderboard.yml: replace the direct commit/push with
  peter-evans/create-pull-request@v7 (branch eval-results), add
  pull-requests: write. Merging that PR triggers the Pages deploy (which
  watches evals/results.json) to publish real numbers.
- evals/README documents the PR flow + the required "Allow GitHub Actions to
  create and approve pull requests" setting.


Claude-Session: https://claude.ai/code/session_016JWn5jRD5tcEFKrubjQ6Px

Co-authored-by: Claude <noreply@anthropic.com>

2026-06-18 13:33:15 +01:00

..

ISSUE_TEMPLATE

Add files via upload

2026-04-05 13:10:04 +01:00

workflows

Leaderboard workflow: open a PR instead of pushing to protected main (#45)

2026-06-18 13:33:15 +01:00

FUNDING.yml

Create FUNDING.yml

2026-02-20 12:15:54 +00:00

PULL_REQUEST_TEMPLATE.md

Add files via upload

2026-04-05 13:10:04 +01:00