chore: rename scripts/test-branch-on-hetzner to test-on-hetzner - #753
Merged
Conversation
brawer
force-pushed
the
rename-test-branch-on-hetzner
branch
3 times, most recently
from
August 23, 2026 07:39
5290065 to
72a97a7
Compare
It's not just for testing a branch anymore -- deploy --image/--branch, start --containerized, validate, and the bucket lifecycle all work identically whether the container was built from a dev branch or pulled as an already-built release image (verified end-to-end: the #749 investigation ran the fix straight from main, and the very next smoke test used a real v0.8.0 release image, through the exact same containerized path). 'test-branch-on-hetzner' undersold that for a while. Pure rename plus reference updates (README.md/cloud_test.py's own opening lines included, since those undersold it too) -- no logic changes. git mv preserved history; CI workflow triggers didn't need touching (scripts/**, **/*.sh globs, not hardcoded to the old path). Co-Authored-By: Claude Sonnet 5 <noreply@anthropic.com>
brawer
force-pushed
the
rename-test-branch-on-hetzner
branch
from
August 23, 2026 07:40
72a97a7 to
e7190c6
Compare
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.
What
Pure rename:
scripts/test-branch-on-hetzner/→scripts/test-on-hetzner/, plus updating every reference to the old path.Why
It's not just for testing a branch anymore.
deploy --image/--branch,start --containerized,validate, and the bucket lifecycle all work identically whether the container was built from a dev branch or pulled as an already-built release image -- verified end-to-end today: the #749 investigation ran the fix straight frommain, and the very next smoke test used a realv0.8.0release image, through the exact same containerized path.test-branch-on-hetznerundersold that.Scope
git mv(preserves history) plus reference updates inscripts/README.md,scripts/test-branch-on-macos/{README.md,test_macos.py},docs/TESTING.md,.github/workflows/{test-scripts,shellcheck}.yml(comments only -- their actual path-filter triggers arescripts/**/**/*.shglobs, not hardcoded to the old directory name, so no trigger changes needed), andsrc/pipeline/osm/fetch.rs's one comment. Also tightened the tool's own opening lines (README.md's title,cloud_test.py's module docstring), which still described it as branch-only.No logic changes.
uv run pytest(78/78),cargo build, anduvx ruff check(same 2 pre-existing findings as before) all clean from the new location.🤖 Generated with Claude Code