Skip to content

chore: backports can trigger CI #9232

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.

Sign up for GitHub

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

Merged
owlstronaut merged 1 commit into from
Apr 14, 2026
+5 −0
Merged

chore: backports can trigger CI #9232

Changes from all commits
Commits
Show all changes
1 commit
Select commit
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
5 changes: 5 additions & 0 deletions scripts/backport.js
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -95,6 +95,11 @@ module.exports = async ({ github, context, core }) => {
base: target,
})

// Trigger CI on the backport branch. Events from GITHUB_TOKEN don't trigger workflows, but workflow_dispatch is an explicit exception to that rule.
await github.rest.actions.createWorkflowDispatch({
owner, repo, workflow_id: 'ci.yml', ref: branch,
})

results.push(`🎉 Backport to \`${target}\` created: #${backportPr.number}`)
core.info(`Created backport PR #${backportPr.number} for ${target}`)
} catch (error) {
Expand Down
Loading