Skip to content
This repository has been archived by the owner on Feb 22, 2022. It is now read-only.

State prerequisites in README.md explicitly #30

Merged
merged 1 commit into from
Nov 15, 2019

Conversation

aliok
Copy link
Member

@aliok aliok commented Nov 13, 2019

State prerequisites in README.md explicitly.

Comments inline.

@knative-prow-robot
Copy link
Contributor

Hi @aliok. Thanks for your PR.

I'm waiting for a knative member to verify that this patch is reasonable to test. If it is, they should reply with /ok-to-test on its own line. Until that is done, I will not automatically test new commits in this PR, but the usual testing commands by org members will still work. Regular contributors should join the org to skip this step.

Once the patch is verified, the new status will be reflected by the ok-to-test label.

I understand the commands that are listed here.

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.

@@ -46,6 +46,17 @@ EOF
Please refer to [Building the Operator Image](#building-the-operator-image) to
build your own image.

## Prerequisites
Copy link
Member Author

@aliok aliok Nov 13, 2019

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

This header was referenced above ("...Please make sure the [prerequisites](#Prerequisites) are installed first...")

Comment on lines -61 to 74
kubectl get eventings.operator.knative.dev -oyaml
kubectl get eventing -oyaml
kubectl get eventings.operator.knative.dev
kubectl get eventing
kubectl get ke
```
Copy link
Member Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Added ke as well.
Got rid of -oyaml as it proves no point here.

@googlebot
Copy link

We found a Contributor License Agreement for you (the sender of this pull request), but were unable to find agreements for all the commit author(s) or Co-authors. If you authored these, maybe you used a different email address in the git commits than was used to sign the CLA (login here to double check)? If these were authored by someone else, then they will need to sign a CLA as well, and confirm that they're okay with these being contributed to Google.
In order to pass this check, please resolve this problem and then comment @googlebot I fixed it.. If the bot doesn't comment, it means it doesn't think anything has changed.

ℹ️ Googlers: Go here for more info.

@aliok
Copy link
Member Author

aliok commented Nov 13, 2019

@googlebot I fixed it..

@aliok
Copy link
Member Author

aliok commented Nov 13, 2019

/assign @n3wscott

@houshengbo
Copy link

@aliok Plz make sure you sign the CLA.

@aliok
Copy link
Member Author

aliok commented Nov 13, 2019

@houshengbo I've already signed it.

Let me push force and remove @mattmoor co-authored commit. Maybe there's a problem with his CLA.

UPDATE: did that and it is fixed!

@googlebot
Copy link

CLAs look good, thanks!

ℹ️ Googlers: Go here for more info.

@houshengbo
Copy link

/approve
/lgtm
Thx!!!

@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: aliok, houshengbo

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 /approve in a comment
Approvers can cancel approval by writing /approve cancel in a comment

README.md Outdated Show resolved Hide resolved
* [`ko`](https://github.com/google/ko)

Install `ko` with the following command, if it is not available on your machine:
```

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

README.md:54: MD031 Fenced code blocks should be surrounded by blank lines

@houshengbo
Copy link

@aliok Would u minding changing one more time based on the comments from the build job??

@aliok
Copy link
Member Author

aliok commented Nov 15, 2019

cc @houshengbo fixed the test failures

@n3wscott
Copy link
Contributor

/ok-to-test
/lgtm

Sign up for free to subscribe to this conversation on GitHub. Already have an account? Sign in.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

6 participants