Skip to content
New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

fix README for community Dart sample #1180

Merged
merged 1 commit into from
Apr 15, 2019

Conversation

mockturtl
Copy link
Contributor

Replace pubspec field private with publish_to.

See 52f464f.

ref

Replace pubspec field `private` with `publish_to`.  [ref](https://www.dartlang.org/tools/pub/pubspec#publish_to)

See @52f464f.
@knative-prow-robot knative-prow-robot added the size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. label Apr 14, 2019
@googlebot
Copy link

So there's good news and bad news.

👍 The good news is that everyone that needs to sign a CLA (the pull request submitter and all commit authors) have done so. Everything is all good there.

😕 The bad news is that it appears that one or more commits were authored or co-authored by someone other than the pull request submitter. We need to confirm that all authors are ok with their commits being contributed to this project. Please have them confirm that here in the pull request.

Note to project maintainer: This is a terminal state, meaning the cla/google commit status will not change from this state. It's up to you to confirm consent of all the commit author(s), set the cla label to yes (if enabled on your project), and then merge this pull request when appropriate.

ℹ️ Googlers: Go here for more info.

@googlebot googlebot added the cla: no Indicates the PR's author has not signed the CLA. label Apr 14, 2019
@knative-prow-robot knative-prow-robot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 14, 2019
@mockturtl mockturtl changed the base branch from release-0.5 to master April 14, 2019 22:45
@knative-prow-robot knative-prow-robot added size/XS Denotes a PR that changes 0-9 lines, ignoring generated files. and removed size/XXL Denotes a PR that changes 1000+ lines, ignoring generated files. labels Apr 14, 2019
@samodell
Copy link
Contributor

/ok-to-test

@knative-prow-robot knative-prow-robot removed the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Apr 15, 2019
@samodell
Copy link
Contributor

@mockturtl Please see the bot's comment about signing the CLA. If you think you already have, the most common issue with the CLA bot is the email used to sign your git commits being different from the email you used to sign the CLA. As soon as that's resolved, we'll get this merged in.

@mockturtl
Copy link
Contributor Author

Hi @samodell, thanks! I've signed the CLA (The good news is that everyone that needs to sign a CLA ... have done so. Everything is all good there).

I think the bot was tripped because I targeted my patch for the release-0.5 branch instead of master (my parent), which dragged in the whole diff between them.

I fixed that...

mockturtl changed the base branch from release-0.5 to master 18 hours ago

...so the PR no longer includes other people's code (it appears that one or more commits were authored or co-authored by someone other than the pull request submitter).

@samodell
Copy link
Contributor

Ah, that's what I get for skimming. I'll override the CLA bot, then.

/approve
/lgtm

@knative-prow-robot knative-prow-robot added the lgtm Indicates that a PR is ready to be merged. label Apr 15, 2019
@knative-prow-robot
Copy link
Contributor

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: mockturtl, samodell

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

@samodell samodell added cla: yes Indicates the PR's author has signed the CLA. and removed approved cla: no Indicates the PR's author has not signed the CLA. labels Apr 15, 2019
@googlebot
Copy link

A Googler has manually verified that the CLAs look good.

(Googler, please make sure the reason for overriding the CLA status is clearly documented in these comments.)

ℹ️ Googlers: Go here for more info.

@knative-prow-robot knative-prow-robot merged commit de30848 into knative:master Apr 15, 2019
samodell pushed a commit to samodell/docs that referenced this pull request Apr 23, 2019
Replace pubspec field `private` with `publish_to`.  [ref](https://www.dartlang.org/tools/pub/pubspec#publish_to)

See @52f464f.
@samodell samodell mentioned this pull request Apr 24, 2019
knative-prow-robot pushed a commit that referenced this pull request Apr 24, 2019
* Knative with Gardener - Fix Installing Istio Typo (#1027)

* Update installation documentation with Minishift (#1114)

* Remove usage of kubectl. Using oc instead

* Update webhook admissions

* Mention IKS's one-click install process (#1131)

Signed-off-by: Doug Davis <[email protected]>

* helloworld-go: install CA certs (#1143)

* helloworld-go: install CA certs

All users who are querying any HTTPS endpoints will need this and won't understand why it's failing.

* address fixes

Signed-off-by: Ahmet Alp Balkan <[email protected]>

* Use istio-ingressgateway servce as this is the new one used in Knative 0.3 and above (#1171)

* knative.slack.com -> slack.knative.dev (#1176)

* Update Knative-custom-install.md (#1178)

change the name `release.yaml` to `build.yaml`

* fix README (#1180)

Replace pubspec field `private` with `publish_to`.  [ref](https://www.dartlang.org/tools/pub/pubspec#publish_to)

See @52f464f.
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
cla: yes Indicates the PR's author has signed the CLA. 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.

4 participants