chore: move to the evalshift GitHub org - #31
Merged
Merged
Conversation
The repositories moved from the babaliauskas account to the evalshift organization. Point links, PyPI project URLs, mkdocs metadata, the release dispatch, the init --ci scaffold and the docs at evalshift/*. The CI pin check now matches evalshift/evalshift-action steps and still matches the old babaliauskas/evalshift-action name, which GitHub redirects, comparing owner and repo case-insensitively as GitHub does. Historical CHANGELOG entries and plan/spec docs keep the old name. Co-Authored-By: Claude Opus 5.5 (1M context) <noreply@anthropic.com>
babaliauskas
force-pushed
the
chore/move-to-evalshift-org
branch
from
October 2, 2026 20:17
d9a5e79 to
6478d71
Compare
babaliauskas
changed the title
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.
Summary
The repos moved from
babaliauskasto theevalshiftorg. This points everything atevalshift/*:pyproject.tomlproject URLs): reaches PyPI with the next release.docs/*,llms-full.txt, mkdocs metadata, examples.initconfig header, theinit --ciworkflow scaffold (uses: evalshift/evalshift-action@v0), and the HTML report footer. The footer and header still linked the pre-renamebabaliauskas/EvalShiftrepo.notify-action-reponow dispatches toevalshift/evalshift-action.utils/ci_pin.py): matchesevalshift/evalshift-actionand still matchesbabaliauskas/evalshift-action. GitHub redirects the old name, so users' existing workflows keep it. Owner and repo are compared case-insensitively, as GitHub does.Historical CHANGELOG entries, plan/spec docs and the LICENSE copyright are unchanged on purpose.
Before the next release (manual)
evalshift→ Publishing, add ownerevalshift, repoevalshift-cli, workflowrelease.yml, environmentpypi, then remove thebabaliauskasentry. Without this the publish job fails.EVALSHIFT_ACTION_DISPATCH_TOKEN(optional, currently unset): if you add it, the fine-grained PAT's resource owner must beevalshift.Test plan
ruff check,ruff format --check,mypy --strict src/evalshift_clipytest --cov-fail-under=90: 2451 passed, 94.5% coverage. The one local failure istest_the_vendored_schema_matches_the_server_export, which compares against a sibling server checkout on a feature branch. It fails the same way on untouchedmainand is skipped in CI.*/evalshift-actionis ignored.🤖 Generated with Claude Code