-
Notifications
You must be signed in to change notification settings - Fork 31
CI: Trigger examples update when a create-plugin release happens #1824
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
base: main
Are you sure you want to change the base?
Conversation
Hello! 👋 This repository uses Auto for releasing packages using PR labels. ✨ This PR can be merged. It will not be considered when calculating future versions of the npm packages and will not appear in the changelogs. |
@@ -445,3 +445,14 @@ jobs: | |||
# comes from the get-secrets step (shared get-vault-secrets workflow) | |||
SLACK_WEBHOOK_URL: ${{ env.SLACK_WEBHOOK_URL }} | |||
run: npm run release | |||
|
|||
- name: Trigger examples update | |||
run: | |
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Is it much of an issue if this triggers examples repo CI on every merge to main?
There was a problem hiding this comment.
Choose a reason for hiding this comment
The reason will be displayed to describe this comment to others. Learn more.
Good point. I should add a check to only if files inside create-plugin package were touched
What this PR does / why we need it:
Trigger an update of the examples whenever a new release of create-plugin happens
Which issue(s) this PR fixes:
Fixes #
Special notes for your reviewer: