-
Notifications
You must be signed in to change notification settings - Fork 773
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
Merge requirements into getting-started page #845
Comments
Issue-Label Bot is automatically applying the label Links: app homepage, dashboard and code for this bot. |
I've marked this one for tackling during the Kubeflow Doc Sprint. This is a good task for a tech writer to tackle during the sprint. |
This one seems like a good place to get started, please assign it to me when you have a chance! |
/assign @OfficePop |
Changes have been added to kubeflow/website PR 923. |
Did someone else resolve this issue? Had to remove the related updates from my original PR because it was causing merge conflicts. If it's still outstanding, let me know and i'll submit a separate PR for it once the original is handled. |
This issue is not yet resolved. The page is still in the docs: As far as I know there's no PR in flight to move the content to the getting-started page. There was a change to the requirements page, that swapped ksonnet to kustomize. That change probably caused the merge conflict. Please do go ahead with this change, if you have the bandwidth. |
Excellent, I've edited the previous comment with current PR. |
Glad to be wrong on this, thanks for adding that change in OfficePop |
/close |
@sarahmaddox: Closing this issue. In response to this:
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. |
Merge the "requirements" page (https://www.kubeflow.org/docs/started/requirements/) into the getting-started guide (https://www.kubeflow.org/docs/started/getting-started/) and add the appropriate redirect.
The text was updated successfully, but these errors were encountered: