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

Add MLObs onboarding docs to gitbook #538

Merged
merged 2 commits into from
Feb 19, 2024
Merged

Conversation

eric-lidong
Copy link
Contributor

Description

Adding gitbook reference to the MLobs related documentation, including the model schema and the mlobs onboarding guide.

Modifications

Add gitbook summary reference for new docs, fixed one heading typo in mlobs onboarding guide.

Tests

-->

Checklist

  • Added PR label
  • Added unit test, integration, and/or e2e tests
  • Tested locally
  • Updated documentation
  • Update Swagger spec if the PR introduce API changes
  • Regenerated Golang and Python client if the PR introduces API changes

Release Notes


@eric-lidong eric-lidong added the documentation Improvements or additions to documentation label Feb 16, 2024
@eric-lidong eric-lidong self-assigned this Feb 16, 2024
@eric-lidong eric-lidong merged commit 78ef985 into caraml-dev:main Feb 19, 2024
24 of 26 checks passed
leonlnj pushed a commit that referenced this pull request Feb 20, 2024
<!--  Thanks for sending a pull request!  Here are some tips for you:

1. Run unit tests and ensure that they are passing
2. If your change introduces any API changes, make sure to update the
e2e tests
3. Make sure documentation is updated for your PR!

-->
# Description
Adding gitbook reference to the MLobs related documentation, including
the model schema and the mlobs onboarding guide.

# Modifications
Add gitbook summary reference for new docs, fixed one heading typo in
mlobs onboarding guide.

# Tests

-->

# Checklist
- [ ] Added PR label
- [ ] Added unit test, integration, and/or e2e tests
- [ ] Tested locally
- [ ] Updated documentation
- [ ] Update Swagger spec if the PR introduce API changes
- [ ] Regenerated Golang and Python client if the PR introduces API
changes

# Release Notes
<!--
Does this PR introduce a user-facing change?
If no, just write "NONE" in the release-note block below.
If yes, a release note is required. Enter your extended release note in
the block below.
If the PR requires additional action from users switching to the new
release, include the string "action required".

For more information about release notes, see kubernetes' guide here:
http://git.k8s.io/community/contributors/guide/release-notes.md
-->

```release-note

```
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
documentation Improvements or additions to documentation
Projects
None yet
Development

Successfully merging this pull request may close these issues.

2 participants