Skip to content

Check CI for private machine, person, and agent names - #10

Merged
myobie merged 1 commit into
mainfrom
agent/private-names
Sep 29, 2026
Merged

myobie merged 1 commit into
mainfrom
agent/private-names

Conversation

@myobie

@myobie myobie commented Sep 29, 2026

Copy link
Copy Markdown
Contributor

Adds scripts/check-private-names.py and a Private names workflow, the same check pty, pty-relay, pty-layout and transplant run. It fails on the fleet's machine names (stored as SHA-256 digests), /home/USER and /Users/USER paths other than example, real person/ IDs, and agent/fleet/, mission/fleet/ or mission-run/fleet/ IDs. --self-test proves it still catches each kind. Lines that must stay go in .private-names-allow.

This repository passes it as it stands, so the PR adds only the check.

Public repositories hold invented examples only: no machine or host
names, no personal home paths, no real person IDs, and no internal
agent or mission IDs. scripts/check-private-names.py enforces that on
every pull request and push to main, and --self-test proves it still
catches each kind. It is the same script as in pty, pty-relay,
pty-layout and transplant. This repository passes it as it stands.
@myobie
myobie merged commit 4d1e762 into main Sep 29, 2026
2 checks passed
@myobie
myobie deleted the agent/private-names branch September 29, 2026 17:23
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