Skip to content
This repository was archived by the owner on Dec 1, 2022. It is now read-only.

🤖 Triggering CI on branch 'release-next' after synching to upstream/master#4

Merged
openshift-merge-robot merged 1 commit intorelease-nextfrom
release-next-ci
Jun 21, 2019
Merged

🤖 Triggering CI on branch 'release-next' after synching to upstream/master#4
openshift-merge-robot merged 1 commit intorelease-nextfrom
release-next-ci

Conversation

@alanfx
Copy link
Copy Markdown

@alanfx alanfx commented Jun 19, 2019

No description provided.

@openshift-ci-robot openshift-ci-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. approved Indicates a PR has been approved by an approver from all required OWNERS files. labels Jun 19, 2019
@navidshaikh
Copy link
Copy Markdown

/retest

@rhuss
Copy link
Copy Markdown

rhuss commented Jun 19, 2019

@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 ?

@navidshaikh
Copy link
Copy Markdown

@rhuss :

I guess the PR needs to be rebased on master first (as this is still the release-next-ci branch)

Yup.

I suggest just to merge and wait for tomorrow nights PR ?

We can run https://github.com/openshift/knative-client/blob/master/openshift/release/update-to-head.sh to update release-next and release-next-ci branches to update same PR, I just ran same above.

@navidshaikh
Copy link
Copy Markdown

Failure of tests complains

🔥 No license header found in:
   ./openshift/olm/knative-serving.catalogsource.yaml

@navidshaikh
Copy link
Copy Markdown

/lgtm

@openshift-ci-robot openshift-ci-robot added the lgtm Indicates that a PR is ready to be merged. label Jun 21, 2019
@openshift-ci-robot
Copy link
Copy Markdown

[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

Details Needs approval from an approver in each of these files:

Approvers can indicate their approval by writing /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

@openshift-merge-robot openshift-merge-robot merged commit c9ef507 into release-next Jun 21, 2019
@alanfx
Copy link
Copy Markdown
Author

alanfx commented Jun 21, 2019

Hm, not sure why the webhook didn't merge this PR. I'll take a look

alanfx pushed a commit that referenced this pull request Mar 10, 2021
…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
Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.

Labels

approved Indicates a PR has been approved by an approver from all required OWNERS files. kind/sync-fork-to-upstream lgtm Indicates that a PR is ready to be merged. size/XS Denotes a PR that changes 0-9 lines, ignoring generated files.

Projects

None yet

Development

Successfully merging this pull request may close these issues.

5 participants