Skip to content

feat: send x-sato-repo so Sato Hub can tell its own CI runs from yours - #5

Merged
satohubai merged 1 commit into
mainfrom
feat/x-sato-repo-header
Oct 1, 2026
Merged

satohubai merged 1 commit into
mainfrom
feat/x-sato-repo-header

Conversation

@satohubai

Copy link
Copy Markdown
Owner

Each call to the Sato Hub API now carries x-sato-repo: <owner>/<repo> from GITHUB_REPOSITORY (only when it is a well-formed owner/repo).

Sato Hub uses it for one thing: telling its own CI runs of this Action apart from yours, so outside use is never mislabelled as ours. The server stores only an own/not-own flag (plus the org name for Sato Hub's own orgs), never a repo name. Server side: amateokap/onchain-agent#220 (deployed).

Tests: custody/policy/drift suites pass, incl. new tests for the header helper and both fetch paths.

🤖 Generated with Claude Code

Every call to the Sato Hub API now carries x-sato-repo: <owner>/<repo>
(from GITHUB_REPOSITORY). The server uses it only to flag Sato Hub's own CI
runs of this Action as ours; it stores an own/not-own flag, never the repo
name. Nothing is sent when GITHUB_REPOSITORY is absent or malformed.

Co-Authored-By: Claude Opus 5.5 <noreply@anthropic.com>
@satohubai
satohubai merged commit 5841fce into main Oct 1, 2026
1 check passed
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant