Repository navigation
Add CI workflow for Tiny Wire drift check - #1
Merged
Merged
Conversation
Runs scripts/check-tinywire-drift.sh on pushes to main and on pull requests. Checks out tiny-wire at the tag matching lib/.tinywire-version into a sibling directory, which is the layout the script expects. Claude-Session: https://claude.ai/code/session_0154NnBLzCYzuy9YoR5jcKrV
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.
Adds
.github/workflows/tinywire-drift.yml, which runsscripts/check-tinywire-drift.shin CI on pull requests and on pushes tomain(the Pages deploy path). Feature-branch pushes are covered by the PR trigger, so each PR runs the check once instead of twice.The script expects a tiny-wire checkout as a sibling of the repo root, so the workflow checks out this repo into
agentic-trust-devtools/andLinzLos/tiny-wireintotiny-wire/side by side under the workspace — the script's defaultTW_REPO_DIRresolves to that layout with no env var needed.Upstream has version tags (
git ls-remote --tagsshowsv1.6), so a step reads the pin fromlib/.tinywire-versionand checks out tagv<pin>. This validates the vendoredlib/files byte-for-byte against the pinned release and catches hand-edits or a pin pointing at a nonexistent tag; a newer upstream release surfaces when the consumer re-syncs viascripts/sync-tinywire.sh, as the workflow comment notes.Verified locally: cloned tiny-wire at
v1.6and ran the script against it —OK — vendored Tiny Wire is in sync (v1.6).No changes to
lib/or the version pin.🤖 Generated with Claude Code
https://claude.ai/code/session_0154NnBLzCYzuy9YoR5jcKrV
Generated by Claude Code