[mergify] Backport to v1.6-branch on request-backport-supported#72757
Open
Alami-Amine wants to merge 1 commit into
Open
[mergify] Backport to v1.6-branch on request-backport-supported#72757Alami-Amine wants to merge 1 commit into
Alami-Amine wants to merge 1 commit into
Conversation
Add a backport rule so that PRs labeled request-backport-supported are also cherry-picked to v1.6-branch (in addition to the existing v1.5-branch and v1.4.2-branch targets), and allow the resulting backport-v1.6-branch PRs to auto-merge when CI is green.
Contributor
Merge Protections🟢 Merge protection satisfied — ready to merge. Show 1 satisfied protection🟢 📃 Configuration Change RequirementsMergify configuration change
|
![gemini-code-assist[bot]](https://avatars.githubusercontent.com/in/956858?s=60&v=4){kind=small}
Contributor
There was a problem hiding this comment.
Code Review
This pull request updates the Mergify configuration in .mergify.yml to add a new backport rule for the v1.6-branch when a pull request is merged into master with the request-backport-supported label. It also updates the automatic labeling conditions to include the backport-v1.6-branch label. There are no review comments, so I have no feedback to provide.
Codecov Report✅ All modified and coverable lines are covered by tests. Additional details and impacted files@@ Coverage Diff @@
## master #72757 +/- ##
=======================================
Coverage 56.60% 56.60%
=======================================
Files 1642 1642
Lines 113136 113136
Branches 13245 13245
=======================================
Hits 64044 64044
Misses 49092 49092 ☔ View full report in Codecov by Harness. 🚀 New features to boost your workflow:
|
|
PR #72757: Size comparison from 51d1d76 to b577624 Full report (23 builds for bl602, bl702, bl702l, cc13x4_26x4, cc32xx, efr32, esp32, nrfconnect, psoc6, qpg, realtek, stm32)
|
andy31415
approved these changes
Jun 26, 2026
andy31415
added
sdk-maintainer-approved
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
2 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.
Problem
The
request-backport-supportedlabel currently triggers backports only tov1.5-branchandv1.4.2-branch. There is no rule to backport tov1.6-branch, even though it is a maintained release branch.Change overview
Backport to v1.6-branchrule that cherry-picks the squashed master commit tov1.6-branchwhen a PR carries therequest-backport-supportedlabel (same trigger as the existing v1.5 / v1.4.2 rules).backport-v1.6-branchto theAuto-merge clean backport PRsrule so the resulting backport PRs auto-merge when CI is green and there are no conflicts, consistent with the other backport targets.The existing
request-backport-sve->v1.6-sve-branchrule is unchanged.Testing
.mergify.ymlparses as well-formed YAML.