chore(ci): sanitize branch names for connect popup build#18700
chore(ci): sanitize branch names for connect popup build#18700
Conversation
41fb3d2 to
3fa72c9
Compare
|
✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found. |
|
✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found. |
| - name: Sanitize branch name for URLs | ||
| id: sanitize_branch | ||
| run: | | ||
| echo "sanitized_branch=$(echo '${{ steps.extract_branch.outputs.branch }}' | tr -d '+#@&=?\\:*')" >> "$GITHUB_OUTPUT" |
There was a problem hiding this comment.
technically, chars ?\:* do not need to be handled because that's an invalid branch name (git won't allow to create it), but I put it there anyway so it's clearer what kind of bugs does this solve
vdovhanych
left a comment
There was a problem hiding this comment.
did we hit this issue somewhere already?
@vdovhanych yes, in the PR of the action run that I linked above I did that and was wondering why connect won't build. I looked at all branches at |
|
/rebase |
3fa72c9 to
77e6d80
Compare
|
✅ Previously successful run of [Test] PR Suite Desktop e2e tests workflow has been found. |
|
✅ Previously successful run of [Test] PR Suite Web e2e tests workflow has been found. |
|
In your example run, the deployment works but all of the tests fail. You also need to escape it in |
vdovhanych
left a comment
There was a problem hiding this comment.
Interesting. I would never even consider using those symbols for branch names, but yeah, if you think it's worth fixing, let's do it. I would just do it for everything, not just connect.
|
Ok @vdovhanych I am closing it.
|
Description
Sanitize branch names for connect popup build base URL
invalid+#@&=branch, successfully deployed here🔍🖥️ Suite web test results: View in Currents
🔍🖥️ Suite desktop test results: View in Currents