Skip to content

Add opsmill/emma to repository dispatch targets#886

Open
petercrocker wants to merge 1 commit intostablefrom
add-emma-repo-dispatch
Open

Add opsmill/emma to repository dispatch targets#886
petercrocker wants to merge 1 commit intostablefrom
add-emma-repo-dispatch

Conversation

@petercrocker
Copy link
Contributor

@petercrocker petercrocker commented Mar 23, 2026

Summary by CodeRabbit

Release Notes

  • Chores
    • Expanded the scope of automated update distribution to reach additional repositories.
  • Add opsmill/emma to the list of repositories notified via repository dispatch workflow

Test plan

  • Verify the workflow YAML is valid
  • Confirm dispatch triggers correctly for the new repository on next SDK release

@github-actions github-actions bot added the group/ci Issue related to the CI pipeline label Mar 23, 2026
@coderabbitai
Copy link

coderabbitai bot commented Mar 23, 2026

No actionable comments were generated in the recent review. 🎉

ℹ️ Recent review info
⚙️ Run configuration

Configuration used: Organization UI

Review profile: CHILL

Plan: Pro

Run ID: 2971c91d-c534-454f-90bf-441b188925a2

📥 Commits

Reviewing files that changed from the base of the PR and between b69690b and 26fb7be.

📒 Files selected for processing (1)
  • .github/workflows/repository-dispatch.yml

Walkthrough

The change modifies the repository dispatch workflow configuration to include an additional repository (opsmill/emma) in the matrix of repositories that receive dispatch events. When the workflow triggers, it will now send a trigger-infrahub-sdk-python-update event to this newly added repository using the existing dispatch logic and payload structure. This is a single-line addition with no modifications to the dispatch event handling mechanism itself.

🚥 Pre-merge checks | ✅ 2 | ❌ 1

❌ Failed checks (1 inconclusive)

Check name Status Explanation Resolution
Description check ❓ Inconclusive The description provides a clear summary and test plan, but lacks detail on behavioral impact, deployment considerations, and other template sections appropriate for the change. Expand the description to include 'What changed' (behavioral/implementation details) and 'Impact & rollout' sections to clarify the change's scope and deployment implications.
✅ Passed checks (2 passed)
Check name Status Explanation
Title check ✅ Passed The title directly and clearly describes the main change: adding opsmill/emma to repository dispatch targets, which matches the single-line code change.
Docstring Coverage ✅ Passed No functions found in the changed files to evaluate docstring coverage. Skipping docstring coverage check.

✏️ Tip: You can configure your own custom pre-merge checks in the settings.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share

Comment @coderabbitai help to get the list of available commands and usage tips.

@cloudflare-workers-and-pages
Copy link

Deploying infrahub-sdk-python with  Cloudflare Pages  Cloudflare Pages

Latest commit: 26fb7be
Status: ✅  Deploy successful!
Preview URL: https://ce635d87.infrahub-sdk-python.pages.dev
Branch Preview URL: https://add-emma-repo-dispatch.infrahub-sdk-python.pages.dev

View logs

@petercrocker petercrocker requested review from a team and fatih-acar March 23, 2026 14:44
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

group/ci Issue related to the CI pipeline

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants