ci: add sync release branches composite action [ED-25426] - #51
Merged
davseve merged 4 commits intoAug 31, 2026
Merged
Conversation
Add reusable composite action that cherry-picks merged PRs across release/stable, release/beta, and main using isolated git worktrees. Ref: ED-25426 Co-authored-by: Cursor <cursoragent@cursor.com>
5 tasks
Ref: ED-25426 Co-authored-by: Cursor <cursoragent@cursor.com>
Merge the merged commit into sync branches and open normal PRs with the original title instead of cherry-pick PRs. Ref: ED-25426 Co-authored-by: Cursor <cursoragent@cursor.com>
Ref: ED-25426 Co-authored-by: Cursor <cursoragent@cursor.com>
davseve
added a commit
to elementor/elementor
that referenced
this pull request
Aug 31, 2026
## Summary - Adds `.github/workflows/sync-release-branches.yml` for the new release branch model - On merge to `release/stable`, automatically opens PRs to `release/beta` and `main` - On merge to `release/beta`, automatically opens a PR to `main` - Uses shared action `elementor/elementor-editor-github-actions/actions/sync-release-branches@main` - Skips PRs whose head branch starts with `sync-pr` to prevent cascade loops ## Test plan - [ ] Merge elementor/elementor-editor-github-actions#51 first - [ ] Merge this PR - [ ] Merge a test PR to `release/stable` and verify sync PRs are created for `release/beta` and `main` - [ ] Merge a test PR to `release/beta` and verify sync PR to `main` - [ ] Verify auto-generated `sync-pr*` PRs do not re-trigger the workflow ## Jira ED-25426 <!--start_gitstream_placeholder--> ### ✨ PR Description ## 1. Problem & Context Automates cherry-pick propagation from stable/beta release branches to downstream branches, reducing manual sync overhead post-merge (ED-25426). ## 2. What Changed (Where) - `.github/workflows/sync-release-branches.yml`: New workflow triggering on merged PRs to release/stable and release/beta branches. ## 3. How It Works Workflow fires on PR merge to release branches (excluding sync-pr prefixed branches), logs merge metadata, then delegates cherry-pick logic to `elementor-editor-github-actions/sync-release-branches` action, passing PR context and authentication. ## 4. Risks Depends on external action stability and correct `GH_PAT` secret configuration; failed syncs won't block original merges but could silently drop cherry-picks if action fails silently. _Generated by LinearB AI and added by gitStream._ <sub>AI-generated content may contain inaccuracies. Please verify before using. 💡 **Tip:** You can customize your AI Description using **Guidelines** [Learn how](https://docs.gitstream.cm/automation-actions/#describe-changes)</sub> <!--end_gitstream_placeholder--> --------- Co-authored-by: Cursor <cursoragent@cursor.com> Co-authored-by: Svitlana-Dykun <svitlanad@elementor.red> Co-authored-by: ElementorBot <48412871+elementorbot@users.noreply.github.com>
Svitlana-Dykun
approved these changes
Aug 31, 2026
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
actions/sync-release-branchesfor the new release branch modelrelease/stable→ PRs torelease/betaandmainrelease/beta→ PR tomainsync-pr<#>_to_<target>branches (no cherry-pick)Test plan
mainelementorandelementor-prorelease/stableand verify sync PRs open forrelease/betaandmainrelease/betaand verify sync PR opens formainsync-pr*head branches do not re-trigger the cascadeJira
ED-25426