fix: Fix the branch name not encode. #2753
Conversation
Signed-off-by: harrisonliu5 <harrisonliu@kubesphere.io>
|
@harrisonliu5: Adding the "do-not-merge/release-note-label-needed" label because no release-note block was detected, please follow our release note process to remove it. Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
ks-ci-bot
added
kind/bug
harrisonliu5
changed the title
|
/area devops |
|
/assign @JohnNiang |
|
hi @luoyuctl this is the front-end part of the git branch name-related issue. Feel free to help us to test it. Thanks! |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: harrisonliu5, JohnNiang The full list of commands accepted by this bot can be found here. The pull request process is described here
Needs approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
/cherry-pick release-3.2 |
|
@harrisonliu5: once the present PR merges, I will cherry-pick it on top of release-3.2 in a new PR and assign it to you. In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
|
/lgtm |
|
LGTM label has been added. Git tree hash: e5876a744b85e10df65689f107cdd78653a40198
|
|
@harrisonliu5: new pull request created: #2756 In response to this:
Instructions for interacting with me using PR comments are available here. If you have questions or suggestions related to my behavior, please file an issue against the kubernetes/test-infra repository. |
it has been verified that there is no problem, but there is still one last problem to fix . see kubesphere/ks-devops#400. |
Signed-off-by: harrisonliu5 harrisonliu@kubesphere.io
What type of PR is this?
/kind bug
What this PR does / why we need it:
Which issue(s) this PR fixes:
Fixes ##2747
Special notes for reviewers:
Does this PR introduced a user-facing change?
Additional documentation, usage docs, etc.: