Skip to content

fix(ci): tighten PR-ref extraction + tolerate missing PRs in advance-deploy-env - #11

Merged
LukasWodka merged 1 commit into
developfrom
fix/advance-deploy-env-skip-issue-refs
Apr 27, 2026
Merged

fix(ci): tighten PR-ref extraction + tolerate missing PRs in advance-deploy-env#11
LukasWodka merged 1 commit into
developfrom
fix/advance-deploy-env-skip-issue-refs

Conversation

@LukasWodka

Copy link
Copy Markdown
Contributor

Caught via verification test: PR body containing Closes #47 (issue ref) caused the workflow to look up #47 as a PR, which 404s, which aborts the whole job.

Two surgical fixes:

  1. Tighter regex — extract PR refs only from commit subjects, matching (#NNN) (squash merge) and Merge pull request #NNN (merge commit) patterns.
  2. Defensive lookupgh api failure no longer fails the workflow; treats as "not a PR, skip."

🤖 Generated with Claude Code

…deploy-env
Found via verification test on tracebloc/model-zoo#52: a commit body containing
'Closes#47' (an issue ref) caused gh api to fail when looking up #47 as a PR,
which aborted the whole workflow because of set -e.
Two surgical fixes:
1. Extract PR refs from commit *subjects* only — match exact patterns
'(#NNN)' (squash merge) and 'Merge pull request #NNN' (merge commit).
Issue refs in commit bodies are no longer picked up.
2. Wrap the gh api call in '|| RESP=\'{}\'' so a non-PR number degrades to
'skip cleanly' instead of failing the job.
Co-Authored-By: Claude Opus 4.7 (1M context) <noreply@anthropic.com>
@LukasWodka
LukasWodka merged commit 57b4cc4 into developApr 27, 2026
@LukasWodka
LukasWodka deleted the fix/advance-deploy-env-skip-issue-refs branch April 27, 2026 12:37
@LukasWodkaLukasWodka added bug Something isn't working work-type:bug Defect or regression labels Jun 8, 2026
Sign up for freeto join this conversation on GitHub. Already have an account? Sign in to comment

Labels

bugSomething isn't workingwork-type:bugDefect or regression

Projects

None yet

Development

Successfully merging this pull request may close these issues.

2 participants

@LukasWodka@saadqbal