Internal: Update cherry pick workflow [TMZ-1035]#629
Merged
Conversation
Svitlana-Dykun
approved these changes
May 12, 2026
max-zu
approved these changes
May 12, 2026
nicoladj77
approved these changes
May 12, 2026
hein-obox
pushed a commit
that referenced
this pull request
May 12, 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
4 participants
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.
✨ PR Description
1. Problem & Context
Cherry-pick workflow needs tighter guard conditions to prevent unintended triggers. Added repository origin validation to ensure PRs originate from the target repo, not forks.
2. What Changed (Where)
.github/workflows/cherry-pick-pr.yml: Enhanced job condition to validategithub.event.pull_request.head.repo.full_name == github.repository.3. How It Works
Workflow now filters at job-level: merged PR + origin repo match + (closed action OR labeled with
cp_prefix). Prevents fork PRs from triggering cherry-pick logic even if merged in upstream.4. Risks
None. Additive guard condition—stricter filtering eliminates false positives without affecting legitimate cherry-pick scenarios.
Generated by LinearB AI and added by gitStream.
AI-generated content may contain inaccuracies. Please verify before using.
💡 Tip: You can customize your AI Description using Guidelines Learn how