Zephyr 4.x workflow: stabilize CI for renamed forks and slashed branch names#10414
Merged
dgarske merged 1 commit intowolfSSL:masterfrom May 6, 2026
Merged
Conversation
night1rider
changed the title
night1rider
changed the title
dgarske
approved these changes
May 6, 2026
4 tasks
|
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.
The Zephyr 4.x CI workflow occasionally failed in two ways:
log file creation crashed when the branch name contained a
/(e.g.feat/sbom-bomshwas interpreted as a subdirectory), andwest updatehung on a credential prompt when a PR's fork was renamed, deleted, or made private.The workflow now fetches the wolfSSL revision via the upstream repo's
refs/pull/<N>/headref instead ofpull_request.head.repo.clone_url.The test script simplifies the log filename to
<board>_<timestamp>.logso slashes in branch names can no longer break the path.It also exports
GIT_TERMINAL_PROMPT=0beforewest updateso any future auth issue fails fast with a clear error instead of the cryptic "could not read Username" hang.