fix: resolve PR number extraction in forward-port workflow #1621
+1
−1
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
grep -oE '[0-9]+$'withbasenameto extract PR number from URL$'sequence in the grep regex was being consumed by bash's ANSI-C quoting, breaking the commandTest plan
PR_NUMBERis correctly extracted from thegh pr createoutput URLNote
Low Risk
Small change limited to CI workflow scripting; main risk is mis-parsing unexpected
ghoutput formats, butbasenameis simpler and less error-prone than the previous regex.Overview
Fixes the forward-port workflow’s PR-number extraction by replacing the
grep -oE '[0-9]+$'parsing withbasename "$PR_URL", avoiding bash/regex quoting issues that could cause the job to fail and preventing follow-up steps (like labeling) from breaking.Written by Cursor Bugbot for commit 2c4725f. This will update automatically on new commits. Configure here.