Skip to content

ci: trigger selfpatch_demos CI on push to main#244

Open
bburda wants to merge 2 commits intomainfrom
feat/notify-demos-on-main
Open

ci: trigger selfpatch_demos CI on push to main#244
bburda wants to merge 2 commits intomainfrom
feat/notify-demos-on-main

Conversation

@bburda
Copy link
Collaborator

@bburda bburda commented Mar 3, 2026

Pull Request

Summary

Adds a notify-demos job to the CI workflow that dispatches a repository_dispatch event to selfpatch/selfpatch_demos after both jazzy-lint and jazzy-test pass on pushes to main. This keeps the integration demo suite in sync with every gateway merge.

  • Fires only on push to main (skipped on PRs via the if: condition)
  • Waits for jazzy-lint and jazzy-test to both succeed before dispatching
  • Sends client-payload with sha and run_url so the selfpatch_demos job summary can link back to the triggering gateway CI run
  • Uses peter-evans/repository-dispatch@v4 with the DEMOS_DISPATCH_TOKEN secret (fine-grained PAT with contents:write on selfpatch/selfpatch_demos)

Issue


Type

  • Bug fix
  • New feature or tests
  • Breaking change
  • Documentation only

Testing

The notify-demos job will be skipped on this PR (the if: condition evaluates to false for pull_request events). End-to-end validation will happen after both this PR and selfpatch/selfpatch_demos#36 are merged: the next push to main will dispatch ros2_medkit_updated to selfpatch_demos and trigger its CI.

Pre-conditions:


Checklist

  • Breaking changes are clearly described (and announced in docs / changelog if needed)
  • Tests were added or updated if needed
  • Docs were updated if behavior or public API changed

Copilot AI review requested due to automatic review settings March 3, 2026 08:51
Copy link
Contributor

Copilot AI left a comment

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Pull request overview

Adds a downstream CI trigger so that every successful merge to main in ros2_medkit can automatically kick off the integration demo suite in selfpatch/selfpatch_demos, keeping demo Docker builds synchronized with gateway changes.

Changes:

  • Adds a new notify-demos GitHub Actions job gated to push events on main.
  • Configures notify-demos to wait for jazzy-lint and jazzy-test success before dispatching ros2_medkit_updated via repository_dispatch.
  • Includes sha and run_url in client-payload for traceability back to the triggering workflow run.

- Guard against skipped upstream jobs by checking needs.jazzy-lint.result
  and needs.jazzy-test.result == 'success' explicitly
- Replace fragile multi-line >- client-payload with a single-line string
- Add permissions: {} to document the job needs no GITHUB_TOKEN access
- Add comment documenting intentional Humble exclusion policy
@bburda bburda self-assigned this Mar 3, 2026
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.

Trigger selfpatch_demos CI on merge to main

2 participants