chore: add github workflow for updating sample repros on release

[ymc9]

Summary by CodeRabbit

• Chores
  • Introduced a new workflow "Update Samples" that automatically updates specific repositories upon a new release.

[coderabbitai]

Walkthrough

Walkthrough

This update introduces a new GitHub workflow named "Update Samples," which is activated upon the publication of a release. It is designed to run on Ubuntu machines and employs a strategy to update specific repositories through a matrix. The workflow triggers a repository dispatch action using a token, ensuring that the designated repositories are updated in response to the release event.

Changes

File	Change Summary
.github/workflows/update-samples.yml	Adds a new workflow for updating samples on release.

Thank you for using CodeRabbit. We offer it for free to the OSS community and would appreciate your support in helping us grow. If you find it useful, would you consider giving us a shout-out on your favorite social media?

Share

• X
• Mastodon
• Reddit
• LinkedIn

---

Tips

Chat

There are 3 ways to chat with CodeRabbit:

Note: Auto-reply has been disabled for this repository by the repository owner. The CodeRabbit bot will not respond to your replies unless it is explicitly tagged.

• Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
  • @coderabbitai generate unit tests for this file.
  • @coderabbitai modularize this function.
• PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
  • @coderabbitai generate interesting stats about this repository and render them as a table.
  • @coderabbitai show all the console.log statements in this repository.
  • @coderabbitai read src/utils.ts and generate unit tests.
  • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (invoked as PR comments)

• @coderabbitai pause to pause the reviews on a PR.
• @coderabbitai resume to resume the paused reviews.
• @coderabbitai review to trigger a review. This is useful when automatic reviews are disabled for the repository.
• @coderabbitai resolve resolve all the CodeRabbit review comments.
• @coderabbitai help to get help.

Additionally, you can add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.

CodeRabbit Configration File (.coderabbit.yaml)

• You can programmatically configure CodeRabbit by adding a .coderabbit.yaml file to the root of your repository.
• The JSON schema for the configuration file is available here.
• If your editor has YAML language server enabled, you can add the path at the top of this file to enable auto-completion and validation: # yaml-language-server: $schema=https://coderabbit.ai/integrations/coderabbit-overrides.v2.json

CodeRabbit Discord Community

Join our Discord Community to get help, request features, and share feedback.

[coderabbitai]

Review Status

Actionable comments generated: 0

Configuration used: CodeRabbit UI

Commits

Files that changed from the base of the PR and between 7f0b91f and 27c7a7f.

Files selected for processing (1)

• .github/workflows/update-samples.yml (1 hunks)

Additional comments: 4

.github/workflows/update-samples.yml (4)

• 3-5: The trigger for this workflow is correctly set to activate upon the publication of a new release. This aligns with the PR's objective to update sample repositories whenever a new release is published.
• 9-9: Running the job on ubuntu-latest ensures compatibility and reliability. However, consider specifying a more precise version of Ubuntu to avoid potential issues with future updates that could introduce breaking changes.
• 11-19: The matrix strategy is well-implemented to iterate over multiple repositories. This approach enhances the workflow's modularity and scalability, allowing for easy addition or removal of repositories in the future.
• 22-27: The repository dispatch action is correctly configured to trigger updates in the specified repositories using a token. Ensure that the RELEASE_TRIGGER_TOKEN secret is securely stored and has the appropriate permissions for repository dispatch actions across the specified repositories.