chore(workflow): add SDK parity dispatch workflow#9
Conversation
- Introduced a new GitHub Actions workflow for SDK parity dispatch. - Triggers on push and pull request events for changes in the `src` directory and `composer.json`. - Utilizes a reusable workflow from the tapsilat/tapsilat-sdk-parity repository.
There was a problem hiding this comment.
Pull request overview
Adds a new GitHub Actions workflow that dispatches an SDK parity check by invoking a reusable workflow from tapsilat/tapsilat-sdk-parity, and scopes execution to changes in src/** and composer.json.
Changes:
- Introduced
sdk-parity-dispatch.ymlworkflow triggered onpush,pull_request, and manualworkflow_dispatch. - Delegates execution to a reusable workflow in
tapsilat/tapsilat-sdk-parityand inherits secrets.
💡 Add Copilot custom instructions for smarter, more guided reviews. Learn how to get started.
| parity-dispatch: | ||
| uses: tapsilat/tapsilat-sdk-parity/.github/workflows/reusable-sdk-parity-dispatch.yml@main |
There was a problem hiding this comment.
The reusable workflow is referenced via @main, which is mutable. Because this job will execute code from another repository, it’s safer to pin to an immutable ref (a commit SHA or a version tag) to avoid unexpected changes running in this repo’s CI context.
| uses: tapsilat/tapsilat-sdk-parity/.github/workflows/reusable-sdk-parity-dispatch.yml@main | ||
| secrets: inherit |
There was a problem hiding this comment.
secrets: inherit forwards all repository/environment secrets to the called workflow. Given this job calls an external reusable workflow, consider passing only the specific secrets it needs (explicit mapping) and setting explicit minimal permissions for GITHUB_TOKEN to reduce blast radius.
srcdirectory andcomposer.json.