Skip to content

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

Open
wants to merge 4 commits into
base: main
Choose a base branch
from

Conversation

academo
Copy link
Contributor

@academo academo commented May 21, 2025

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:

@academo academo requested review from a team as code owners May 21, 2025 13:45
@academo academo requested a review from s4kh May 21, 2025 13:45
@academo academo requested review from wbrowne and xnyo May 21, 2025 13:45
@academo academo requested a review from jackw May 21, 2025 13:45
@academo academo self-assigned this May 21, 2025
@academo academo moved this from 📬 Triage to 🔬 In review in Plugins Platform / Grafana Community May 21, 2025
Copy link
Contributor

github-actions bot commented May 21, 2025

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.

@academo academo added no-changelog Don't include in changelog and version calculations github_actions Pull requests that update GitHub Actions code labels May 21, 2025
@@ -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: |
Copy link
Collaborator

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?

Copy link
Contributor Author

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

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
github_actions Pull requests that update GitHub Actions code no-changelog Don't include in changelog and version calculations
Projects
Status: 🔬 In review
Development

Successfully merging this pull request may close these issues.

2 participants