docs: Refactor BentoCloud docs #4525

Sherlock113 · 2024-02-23T12:12:29Z

What does this PR address?

Fixes #(issue)

Does the Pull Request follow Conventional Commits specification naming? Here are GitHub's
guide on how to create a pull request.
Does the code follow BentoML's code style, pre-commit run -a script has passed (instructions)?
Did you read through contribution guidelines and follow development guidelines?
Did your changes require updates to the documentation? Have you updated
those accordingly? Here are documentation guidelines and tips on writting docs.
Did you write tests to cover your changes?

Signed-off-by: Sherlock113 <sherlockxu07@gmail.com>

For more information, see https://pre-commit.ci

Refactor BentoCloud docs

9d47c23

Signed-off-by: Sherlock113 <sherlockxu07@gmail.com>

Sherlock113 requested a review from a team as a code owner February 23, 2024 12:12

Sherlock113 requested review from larme and removed request for a team February 23, 2024 12:12

Sherlock113 self-assigned this Feb 23, 2024

Sherlock113 added the documentation Documentation, tutorials, and example projects label Feb 23, 2024

ci: auto fixes from pre-commit.ci

f6f11f0

For more information, see https://pre-commit.ci

Sherlock113 merged commit 69b8a29 into bentoml:main Feb 23, 2024
4 checks passed

Sherlock113 deleted the docrefactor branch February 23, 2024 12:32

aarnphm mentioned this pull request Feb 28, 2024

chore(io): allow implicit pydantic type conversion #4534

Merged

aarnphm mentioned this pull request May 26, 2024

fix(build): make sure to install .tar.gz wheels #4755

Closed