What
Each sibling repo's CI has a repository_dispatch step that notifies robot-code when main advances. This requires a fine-grained PAT stored as an org secret.
Without this token
Cross-repo integration tests only run on:
- PRs to robot-code
- Nightly cron (08:00 UTC)
- Manual
workflow_dispatch
Push-to-main on a sibling does NOT trigger integration tests.
Setup steps
-
Create a fine-grained PAT at https://github.com/settings/personal-access-tokens/new
- Name:
ROBOT_CODE_DISPATCH_TOKEN
- Resource owner:
personalrobotics
- Repository access:
personalrobotics/robot-code only
- Permissions:
Contents: Read, Actions: Write
- Expiration: 90 days (set a calendar reminder to rotate)
-
Add as org secret:
gh secret set ROBOT_CODE_DISPATCH_TOKEN --org personalrobotics --visibility all
-
Test: push a trivial change to any sibling's main and verify robot-code's integration workflow triggers.
Priority
Low — nightly cron catches breakage within 24 hours regardless. This just makes it near-instant.
What
Each sibling repo's CI has a
repository_dispatchstep that notifies robot-code whenmainadvances. This requires a fine-grained PAT stored as an org secret.Without this token
Cross-repo integration tests only run on:
workflow_dispatchPush-to-main on a sibling does NOT trigger integration tests.
Setup steps
Create a fine-grained PAT at https://github.com/settings/personal-access-tokens/new
ROBOT_CODE_DISPATCH_TOKENpersonalroboticspersonalrobotics/robot-codeonlyContents: Read,Actions: WriteAdd as org secret:
Test: push a trivial change to any sibling's
mainand verify robot-code's integration workflow triggers.Priority
Low — nightly cron catches breakage within 24 hours regardless. This just makes it near-instant.