[ML] Fail Backport workflow when CLI reports no-branches with version labels#3055
Open
edsavage wants to merge 1 commit intoelastic:mainfrom
Open
[ML] Fail Backport workflow when CLI reports no-branches with version labels#3055edsavage wants to merge 1 commit intoelastic:mainfrom
edsavage wants to merge 1 commit intoelastic:mainfrom
Conversation
… labels Treat sorenlouv/backport no-branches-exception as an error when the PR had vN.N.N labels so missed backports surface in CI. Emit grouped logs for debug and info files on failure. Co-authored-by: Cursor <cursoragent@cursor.com>
✅ Snyk checks have passed. No issues have been found so far.
💻 Catch issues earlier using the plugins for VS Code, JetBrains IDEs, Visual Studio, and Eclipse. |
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
3 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.
Summary
After #3052 merged with
v9.x.xlabels, the Backport workflow completed green even though the sorenlouv/backport CLI raisedno-branches-exceptionand no backport PRs were created (see https://github.com/elastic/ml-cpp/actions/runs/25476521769).Changes
no-branches-exceptionappears inbackport.debug.logand the PR matched ourvN.N.Nlabel check, the workflow fails with a clear::error::annotation instead of exiting 0.backport.debug.logandbackport.info.login collapsible GitHub Actions groups so investigation does not require downloading raw logs.The defensive branch (
HAS_VERSION_LABELnot true) keeps the previous skip behaviour if the workflow layout changes later.Labels
Please apply
:ml,>enhancementor>build, and version labels as appropriate.Made with Cursor