-
Notifications
You must be signed in to change notification settings - Fork 261
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
Sample API Usage page is a bit confusing #101
Comments
We should consider moving this to the clients repo? cc @sixolet |
I am also happy to submit a PR to the serving API docs to get it up to date with |
`run_lint_tool()` uses markdownlint as the lint tool. Bonus: factor out running a linter against a set of files. Part of knative#101.
* Scripts can customize the behavior by providing their own function, plus pre/post actions. Part of knative#101. Bonuses: * moved documentation to README * added basic tests for the feature * moved the helper tests to a separate directory for clarity * refactored checking if a function exists into a function * test-infra presubmit now uses the default integration test runner * Replace last instance of "type -t" * Make custom flag smoke test a unit test * Explain test objective
As https://github.com/knative/serving/blob/master/docs/spec/normative_examples.md has been replaced by a pointer to the knative client githup repo, I think we can close this issue. The examples that have been used included in this document will be moved more less over to the forthcoming user manual (#650) btw, I think https://github.com/knative/serving/blob/master/docs/spec/normative_examples.md could be completely removed as it looks like that it is not referenced from anywhere |
/kind doc
Expected Behavior
Sample API documentation that works
Actual Behavior
Sample API documentation page here:
https://github.com/knative/serving/blob/master/docs/spec/normative_examples.md#4-deploy-a-revision-from-source
talks about knative tool that doesn't exist and users find it confusing. It would seem clearer to update to use a kubectl example files rather than the tool itself.
Steps to Reproduce the Problem
Additional Info
The text was updated successfully, but these errors were encountered: