🤖 Triggering CI on branch 'release-next' after synching to upstream/master#4
Conversation
|
/retest |
|
@navidshaikh I guess the PR needs to be rebased on master first (as this is still the release-next-ci branch) I suggest just to merge and wait for tomorrow nights PR ? |
12a6d6e to
4d072e2
Compare
25434d1 to
e78a451
Compare
|
@rhuss :
Yup.
We can run https://github.com/openshift/knative-client/blob/master/openshift/release/update-to-head.sh to update |
|
Failure of tests complains |
4d072e2 to
afb6367
Compare
e78a451 to
ceb9e33
Compare
|
/lgtm |
|
[APPROVALNOTIFIER] This PR is APPROVED This pull-request has been approved by: alanfx, navidshaikh The full list of commands accepted by this bot can be found here. The pull request process is described here DetailsNeeds approval from an approver in each of these files:
Approvers can indicate their approval by writing |
|
Hm, not sure why the webhook didn't merge this PR. I'll take a look |
…ve#1246) * # This is a combination of 9 commits. # This is the 1st commit message: adding BUILT-IN SOURCE column for kn source list-types # The commit message #2 will be skipped: # changing list test to check for BUILT-IN SOURCE column # The commit message #3 will be skipped: # changing e2e source list test to check for BUILT-IN SOURCE column # The commit message #4 will be skipped: # adding CHANGELOG entry # The commit message #5 will be skipped: # kn source list-types: changing BUILT-IN SOURCE to BUILT-IN and moving DESCRIPTION column to the end # The commit message #6 will be skipped: # changing BUILT-IN SOURCE to BUILT-IN in changelog # The commit message #7 will be skipped: # Update CHANGELOG.adoc # # Co-authored-by: David Simansky <dsimansk@redhat.com> # The commit message #8 will be skipped: # kn source list-types: changing column header to S, values to X, and moving to second column # The commit message #9 will be skipped: # fixing CHANGELOG merge conflict * adding BUILT-IN SOURCE column for kn source list-types
No description provided.