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

Fixed markdown syntax in Python serving README.md #5206

Merged
merged 1 commit into from
Oct 11, 2022

Conversation

dhruvy1
Copy link
Contributor

@dhruvy1 dhruvy1 commented Aug 31, 2022

This PR fixes markdown syntax in the serving/hello-world/helloworld-python/README.md file. Making it easier to read for new starters.

"Fixes #issue-number" or "Add description of the problem this PR solves"

Proposed Changes

  • Update markdown syntax in serving/hello-world/helloworld-python/README.md file

This PR fixes markdown syntax of the `serving/hello-world/helloworld-python/README.md` file. Making it easier to read for new starters
@linux-foundation-easycla
Copy link

linux-foundation-easycla bot commented Aug 31, 2022

CLA Signed

The committers listed above are authorized under a signed CLA.

  • ✅ login: dhruvy1 / name: Dhruv (f876793)

@netlify
Copy link

netlify bot commented Aug 31, 2022

Deploy Preview for knative ready!

Built without sensitive environment variables

Name Link
🔨 Latest commit f876793
🔍 Latest deploy log https://app.netlify.com/sites/knative/deploys/630f56d5947d2800085c318b
😎 Deploy Preview https://deploy-preview-5206--knative.netlify.app
📱 Preview on mobile
Toggle QR Code...

QR Code

Use your smartphone camera to open QR code link.

To edit notification comments on pull requests, go to your Netlify site settings.

@knative-prow knative-prow bot added the size/L Denotes a PR that changes 100-499 lines, ignoring generated files. label Aug 31, 2022
@knative-prow
Copy link

knative-prow bot commented Aug 31, 2022

Welcome @dhruvy1! It looks like this is your first PR to knative/docs 🎉

@knative-prow knative-prow bot added the needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. label Aug 31, 2022
@knative-prow
Copy link

knative-prow bot commented Aug 31, 2022

Hi @dhruvy1. 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.

@@ -35,7 +35,7 @@ cd knative-docs/code-samples/serving/hello-world/helloworld-python
cd app
```

1. Create a file named `app.py` and copy the following code block into it:
2. Create a file named `app.py` and copy the following code block into it:
Copy link
Contributor

@abrennan89 abrennan89 Aug 31, 2022

Choose a reason for hiding this comment

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

AFAIK the numbers shouldn't need to be specifically called out like this, we should be able to use 1. for each of them, which is easier for future maintenance: https://www.markdownguide.org/basic-syntax/#lists-1

At https://github.com/knative/docs/tree/main/code-samples/serving/hello-world/helloworld-python it looks like it only caused rendering issues because of the broken === "kn" bits, etc. Please leave these as 1. throughout the doc.

Comment on lines +118 to +120
1. Create a new file, `service.yaml` and copy the following service
definition into the file. Make sure to replace `{username}` with your
Docker Hub username or with the URL provided by your container registry
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
1. Create a new file, `service.yaml` and copy the following service
definition into the file. Make sure to replace `{username}` with your
Docker Hub username or with the URL provided by your container registry
1. Create a new file, `service.yaml` and copy the following Service
definition into the file. Make sure to replace `{username}` with your
Docker Hub username or with the URL provided by your container registry:

kubectl apply --filename service.yaml
```
```bash
kubectl apply --filename service.yaml
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
kubectl apply --filename service.yaml
kubectl apply -f service.yaml


With `kn` you can deploy the service with
1. With `kn` you can deploy the service with
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
1. With `kn` you can deploy the service with
1. Create the Service by entering the command:

Comment on lines +153 to +154
This will wait until your service is deployed and ready, and ultimately it
will print the URL through which you can access the service.
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
This will wait until your service is deployed and ready, and ultimately it
will print the URL through which you can access the service.
Once the Service is ready, the URL for the Service is printed in the terminal output.

kubectl delete --filename service.yaml
```
```bash
kubectl delete --filename service.yaml
Copy link
Contributor

Choose a reason for hiding this comment

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

Suggested change
kubectl delete --filename service.yaml
kubectl delete -f service.yaml

@abrennan89
Copy link
Contributor

/ok-to-test
/hold

@knative-prow knative-prow bot added ok-to-test Indicates a non-member PR verified by an org member that is safe to test. do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. and removed needs-ok-to-test Indicates a PR that requires an org member to verify it is safe to test. labels Aug 31, 2022
@abrennan89
Copy link
Contributor

abrennan89 commented Aug 31, 2022

@dhruvy1 thanks for the PR! I've added a few comments, mostly about formatting or suggestions for readability of content.

@abrennan89 abrennan89 removed the do-not-merge/hold Indicates that a PR should not merge because someone has issued a /hold command. label Oct 11, 2022
@abrennan89
Copy link
Contributor

/lgtm
/approve

Would've been nice to have had review comments implemented, but merging anyway since I don't want this issue to get stale.
@dhruvy1 for future PRs, please follow the style guide to ensure docs are consistent. Thanks.

@knative-prow knative-prow bot added the lgtm Indicates that a PR is ready to be merged. label Oct 11, 2022
@knative-prow
Copy link

knative-prow bot commented Oct 11, 2022

[APPROVALNOTIFIER] This PR is APPROVED

This pull-request has been approved by: abrennan89, dhruvy1

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

@knative-prow knative-prow bot added the approved Indicates a PR has been approved by an approver from all required OWNERS files. label Oct 11, 2022
@knative-prow knative-prow bot merged commit 9a3dcf6 into knative:main Oct 11, 2022
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
approved Indicates a PR has been approved by an approver from all required OWNERS files. lgtm Indicates that a PR is ready to be merged. ok-to-test Indicates a non-member PR verified by an org member that is safe to test. size/L Denotes a PR that changes 100-499 lines, ignoring generated files.
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants