Create ROBOT_CODE_DISPATCH_TOKEN for cross-repo CI dispatch

Open Beginner friendly
#7 0 comments 0 reactions 0 assignees View on GitHub

Nobody has claimed this yet.

Assessment

Difficulty
2/5
Estimated time
1-3 hours
Newbie friendliness
72/100
Issue type
Feature
Clarity
Clearly specified
Activity status
Quiet
Tech stack
github, github-actions
Domain
ci-cd, devops

Research direction

Follow the PAT and organization-secret setup steps in this issue, using the listed repository and permissions. Then push a trivial change to a sibling repository’s main branch and verify that robot-code’s integration workflow triggers; done means the secret works and the dispatch occurs.

Written by the indexing model from the issue text.

Description

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

  1. 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)
  2. Add as org secret:

    gh secret set ROBOT_CODE_DISPATCH_TOKEN --org personalrobotics --visibility all
    
  3. 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.

Dominant language
Shell
Stars
3
Forks
1
PR merge metrics
No merged PRs in 30d

Contributor guide

Open the contributing guide

First steps

  1. Read the whole issue, then the project's contributing guide.
  2. Comment on the issue to say you are picking it up — it saves two people doing the same work.
  3. Fork the repository and make your change on a branch.
  4. Open a pull request that references the issue number.

More from personalrobotics/robot-code

All issues in personalrobotics/robot-code

Similar issues

More Shell/Bash issues

Get new issues in your inbox

A short digest of beginner-friendly GitHub issues.