chore: update urls after transfer to FreedomIntelligence org#52
Merged
Conversation
Repo has been transferred from JuhaoLiang1997 (personal) to FreedomIntelligence (organisation). GitHub installs HTTP redirects for github.com/<old>/AccelMark/* automatically, but GitHub Pages does *not* redirect across owners — the live leaderboard URL must be updated explicitly. Replacements (across docs, frontend, leaderboard generator): - juhaoliang1997.github.io/AccelMark → freedomintelligence.github.io/AccelMark - github.com/JuhaoLiang1997/AccelMark → github.com/FreedomIntelligence/AccelMark Intentionally left untouched: - "submitted_by" fields in results/**/result.json and runners/*/meta.json — these record historical attribution under the submitter's actual GitHub identity at submission time and must not change when the repo moves. - pyproject.toml maintainer email (juhaoliang1997@gmail.com) — that is the maintainer's personal address, not a repo URL. - DEVELOPMENT.md submitted_by example value — kept as the real historical handle so the docs match what readers see in results/. Verified: - runners/validate_runners.py: 9/9 folders, hashes intact. - runners/validate_suites.py: 7/7 suites valid. Co-authored-by: Cursor <cursoragent@cursor.com>
…to read
After the FreedomIntelligence transfer, the default GITHUB_TOKEN
permissions are stricter than they were on the personal account.
The "Validate result submissions" job's final step uses
actions/github-script to post a PR summary comment and was failing:
403 Resource not accessible by integration
POST /repos/.../issues/52/comments
x-accepted-github-permissions: issues=read; pull_requests=read
Grant the bare-minimum scope (`pull-requests: write`) on the
validate job only, and lock the workflow default down to
`contents: read` so other jobs continue to run with least privilege
(GitHub's recommended hardening pattern).
Co-authored-by: Cursor <cursoragent@cursor.com>
✅ AccelMark Validation: All submissions validSee the workflow run for details. |
Submissions to the leaderboard are now PR-only: - Remove process_submissions.yml workflow + community_submission.md issue template + runners/gen_pr_summary.py helper. The workflow required org-level "Allow GitHub Actions to create and approve pull requests" (locked off in this org) and also had a script-injection surface when interpolating issue body into shell commands. - Update README.md, CONTRIBUTING.md, ISSUE_TEMPLATE/config.yml, and the home-page CTA to point contributors at the standard fork → PR flow described in CONTRIBUTING.md. - Rewrite openclaw_skill.handle_submit to return copy-pasteable PR instructions (and the finalised result.json) instead of POSTing to the GitHub Issues API; update tests accordingly. - Drop gen_pr_summary.py from the runner-folder skip lists. Co-authored-by: Cursor <cursoragent@cursor.com>
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
1 participant
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Repo has been transferred from JuhaoLiang1997 (personal) to FreedomIntelligence (organisation). GitHub installs HTTP redirects for github.com//AccelMark/* automatically, but GitHub Pages does not redirect across owners — the live leaderboard URL must be updated explicitly.
Replacements (across docs, frontend, leaderboard generator):
Intentionally left untouched:
Verified:
Summary
Type of change
Testing
# Commands used to verifyChecklist
result.jsonfiles (or I have explained the migration path)BenchmarkRunner, produces validresult.json, includes a reference resultvalidate_submission.pyupdated and all existing results still validateleaderboard/generate.pyproduces correct output on existing resultsRelated issues