Skip to content

Conversation

@htahir1
Copy link
Contributor

@htahir1 htahir1 commented Apr 1, 2025

Describe changes

Lots of bits and bobs

Pre-requisites

Please ensure you have done the following:

  • I have read the CONTRIBUTING.md document.
  • I have added tests to cover my changes.
  • I have based my new branch on develop and the open PR is targeting develop. If your branch wasn't based on develop read Contribution guide on rebasing branch to develop.
  • IMPORTANT: I made sure that my changes are reflected properly in the following resources:
    • ZenML Docs
    • Dashboard: Needs to be communicated to the frontend team.
    • Templates: Might need adjustments (that are not reflected in the template tests) in case of non-breaking changes and deprecations.
    • Projects: Depending on the version dependencies, different projects might get affected.

Types of changes

  • Bug fix (non-breaking change which fixes an issue)
  • New feature (non-breaking change which adds functionality)
  • Breaking change (fix or feature that would cause existing functionality to change)
  • Other (add details above)

@htahir1 htahir1 requested a review from strickvl April 1, 2025 08:02
@coderabbitai
Copy link
Contributor

coderabbitai bot commented Apr 1, 2025

Important

Review skipped

Auto reviews are disabled on this repository.

Please check the settings in the CodeRabbit UI or the .coderabbit.yaml file in this repository. To trigger a single review, invoke the @coderabbitai review command.

You can disable this status message by setting the reviews.review_status to false in the CodeRabbit configuration file.


Thanks for using CodeRabbit! It's free for OSS, and your support helps us grow. If you like it, consider giving us a shout-out.

❤️ Share
🪧 Tips

Chat

There are 3 ways to chat with CodeRabbit:

  • Review comments: Directly reply to a review comment made by CodeRabbit. Example:
    • I pushed a fix in commit <commit_id>, please review it.
    • Generate unit testing code for this file.
    • Open a follow-up GitHub issue for this discussion.
  • Files and specific lines of code (under the "Files changed" tab): Tag @coderabbitai in a new review comment at the desired location with your query. Examples:
    • @coderabbitai generate unit testing code for this file.
    • @coderabbitai modularize this function.
  • PR comments: Tag @coderabbitai in a new PR comment to ask questions about the PR branch. For the best results, please provide a very specific query, as very limited context is provided in this mode. Examples:
    • @coderabbitai gather interesting stats about this repository and render them as a table. Additionally, render a pie chart showing the language distribution in the codebase.
    • @coderabbitai read src/utils.ts and generate unit testing code.
    • @coderabbitai read the files in the src/scheduler package and generate a class diagram using mermaid and a README in the markdown format.
    • @coderabbitai help me debug CodeRabbit configuration file.

Note: Be mindful of the bot's finite context window. It's strongly recommended to break down tasks such as reading entire modules into smaller chunks. For a focused discussion, use review comments to chat about specific files and their changes, instead of using the PR comments.

CodeRabbit Commands (Invoked using PR comments)

  • @coderabbitai pause to pause the reviews on a PR.
  • @coderabbitai resume to resume the paused reviews.
  • @coderabbitai review to trigger an incremental review. This is useful when automatic reviews are disabled for the repository.
  • @coderabbitai full review to do a full review from scratch and review all the files again.
  • @coderabbitai summary to regenerate the summary of the PR.
  • @coderabbitai generate docstrings to generate docstrings for this PR.
  • @coderabbitai resolve resolve all the CodeRabbit review comments.
  • @coderabbitai plan to trigger planning for file edits and PR creation.
  • @coderabbitai configuration to show the current CodeRabbit configuration for the repository.
  • @coderabbitai help to get help.

Other keywords and placeholders

  • Add @coderabbitai ignore anywhere in the PR description to prevent this PR from being reviewed.
  • Add @coderabbitai summary to generate the high-level summary at a specific location in the PR description.
  • Add @coderabbitai anywhere in the PR title to generate the title automatically.

Documentation and Community

  • Visit our Documentation for detailed information on how to use CodeRabbit.
  • Join our Discord Community to get help, request features, and share feedback.
  • Follow us on X/Twitter for updates and announcements.

@github-actions github-actions bot added the internal To filter out internal PRs and issues label Apr 1, 2025
@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2025

✅ No broken markdown links found!

@github-actions
Copy link
Contributor

github-actions bot commented Apr 1, 2025

Documentation Link Check Results

Absolute links check passed
Relative links check passed
Last checked: 2025-04-04 08:18:34 UTC

@strickvl strickvl added the documentation Improvements or additions to documentation label Apr 1, 2025
@htahir1 htahir1 removed the request for review from strickvl April 1, 2025 08:18
@htahir1 htahir1 requested a review from strickvl April 4, 2025 07:45
Comment on lines +14 to +15

![ZenML API Redoc](../../../.gitbook/assets/zenml_api_redoc.png)
Copy link
Contributor

Choose a reason for hiding this comment

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

Add a bit of text here about what the redoc version is? just to make it look a bit nicer instead of just two images next to one another?

@htahir1 htahir1 requested a review from strickvl April 4, 2025 08:17
@htahir1 htahir1 merged commit 466abe0 into develop Apr 4, 2025
13 checks passed
@htahir1 htahir1 deleted the doc/fixsomeapidocs branch April 4, 2025 08:22
htahir1 added a commit that referenced this pull request Apr 4, 2025
* Update scheduled pipeline deletion logic

* Update Pro API documentation with new endpoints and features

* Update component-guide.md with icon removal

* Add icons and descriptions for ZenML Pro features

* GITBOOK-10: No subject

* Update table of contents with new overview links

* Update API and SDK README to use "Overview" heading

* Restructure project and organization roles

* Add resource ownership, sharing, and custom roles features

* Add team-based role assignments and best practices

* Update API documentation for ZenML OSS and Pro APIs

* Add Pro API getting started guide to table of contents

* Update API ToC with new section titles

* Update getting-started.md with workspace URL info

* GITBOOK-1: No subject

* GITBOOK-2: No subject

* Remove redundant Getting Started sub-sections

* Apply suggestions from code review

Co-authored-by: Alex Strick van Linschoten <[email protected]>

* Add info on OpenAPI vs ReDoc in getting-started.md

---------

Co-authored-by: Alex Strick van Linschoten <[email protected]>
(cherry picked from commit 466abe0)
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 internal To filter out internal PRs and issues

Projects

None yet

Development

Successfully merging this pull request may close these issues.

3 participants