Custom Step Run Naming

[runllm-pr-agent]

Changes Made

• docs/book/how-to/pipeline-development/build-pipelines/using-a-custom-step-invocation-id.md
  • # Using a custom step invocation ID... --> # Using a custom step invocation ID...: The documentation needs to include a section on setting custom step run names to help users distinguish between multiple invocations of the same step within a pipeline. This addition provides clarity and prevents conflicts, as requested in the improvement to make.
• docs/book/how-to/steps-pipelines/advanced_features.md
  • ### Custom Step Invocation IDsWhen ... --> ### Custom Step Invocation IDsWhen ...: The documentation needs to include a section on setting custom step run names, which is useful for distinguishing multiple invocations of the same step within a pipeline. This update provides a clear explanation, a code example, and additional resources for users seeking more information.
• docs/book/how-to/pipeline-development/build-pipelines/README.md
  • Check below for more advanced ways ... --> Check below for more advanced ways ...: The documentation needs a new section on setting custom step run names to help users distinguish between multiple invocations of the same step within a pipeline. This addition provides clarity and prevents conflicts, as requested in the improvement to make.
• docs/book/user-guide/tutorial/fetching-pipelines.md
  • ## Step 4: Working with StepsWithin... --> ## Step 4: Working with Steps### Cu...: The documentation needs to include a section on setting custom step run names to help users distinguish between multiple invocations of the same step within a pipeline. This addition provides clarity and prevents conflicts by ensuring unique step names.
• docs/book/how-to/steps-pipelines/steps_and_pipelines.md
  • ## Basic Pipelines### Creating a Si... --> ## Basic Pipelines### Creating a Si...: The documentation needs to include a section on setting custom step run names to help users distinguish between multiple invocations of the same step within a pipeline. This addition provides clarity and prevents conflicts, as well as directs users to further resources for more information.
• docs/book/how-to/steps-pipelines/configuration.md
  • ** Configuring and customizing your p... --> Configuring and customizing your p...**: A new section on custom step run naming is added to the documentation to guide users on how to set unique identifiers for step runs using the id parameter. This addresses the user's query about distinguishing multiple invocations of the same step within a pipeline.

[coderabbitai]

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

• X
• Mastodon
• Reddit
• LinkedIn

🪧 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 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.

[CLAassistant]

Thank you for your submission! We really appreciate it. Like many open source projects, we ask that you sign our Contributor License Agreement before we can accept your contribution.

---

runllm seems not to be a GitHub user. You need a GitHub account to be able to sign the CLA. If you have already a GitHub account, please add the email address used for this commit to your account.
_{You have signed the CLA already but the status is still pending? Let us recheck it.}

[github-actions]

🔍 Broken Links Report

Summary

• 📁 Files with broken links: 11
• 🔗 Total broken links: 18
• 📄 Broken markdown links: 13
• 🖼️ Broken image links: 0
• ⚠️ Broken reference placeholders: 5

Details

File	Link Type	Link Text	Broken Path
sdk-docs/example-usages.md	📄	"connect ZenML to your infrastructure"	../how-to/infrastructure-deployment/auth-management/README.md
getting-started/core-concepts.md	⚠️	"Materializers"	broken-reference
getting-started/core-concepts.md	⚠️	"your own custom materializer"	broken-reference
getting-started/system-architectures.md	⚠️	"service connectors"	broken-reference
reference/faq.md	⚠️	"Project templates"	broken-reference
best-practices/set-up-your-repository.md	📄	"Set up repository guide"	../../../how-to/code-repositories/code-repositories.md
best-practices/set-up-your-repository.md	📄	"Set up a repository guide"	../../../how-to/code-repositories/code-repositories.md
best-practices/set-up-your-repository.md	📄	"Organizing Stacks, Pipelines, Models, and Artifacts guide"	../../../how-to/steps-pipelines/steps_and_pipelines.md
best-practices/set-up-your-repository.md	📄	"Access Management and Roles guide"	../../../how-to/tags/tags.md
best-practices/set-up-your-repository.md	📄	"Shared Libraries and Logic for Teams guide"	../../../how-to/stack-components/stack_components.md
best-practices/set-up-your-repository.md	📄	"a registered code repository"	../../../how-to/code-repositories/code-repositories.md
artifacts/visualizations.md	⚠️	"Complex Use Cases"	broken-reference
manage-zenml-server/best-practices-upgrading-zenml.md	📄	"materializers"	/docs/book/how-to/artifacts/materializers.md
manage-zenml-server/best-practices-upgrading-zenml.md	📄	"installation guide"	/docs/book/getting-started/installation.md
steps-pipelines/advanced_features.md	📄	"fetch them after your pipeline is finished"	fetching-pipelines.md
infrastructure-as-code/best-practices.md	📄	"service connector"	../auth-management/README.md
stack-deployment/register-a-cloud-stack.md	📄	"service connector"	../auth-management/service-connectors-guide.md
connecting-to-zenml/README.md	📄	"ZenML is deployed"	/docs/book/getting-started/deploying-zenml/README.md

📂 Full file paths

• /home/runner/work/zenml/zenml/scripts/../docs/book/sdk-docs/example-usages.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/getting-started/core-concepts.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/getting-started/core-concepts.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/getting-started/system-architectures.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/reference/faq.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/user-guide/best-practices/set-up-your-repository.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/user-guide/best-practices/set-up-your-repository.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/user-guide/best-practices/set-up-your-repository.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/user-guide/best-practices/set-up-your-repository.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/user-guide/best-practices/set-up-your-repository.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/user-guide/best-practices/set-up-your-repository.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/artifacts/visualizations.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/manage-zenml-server/best-practices-upgrading-zenml.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/manage-zenml-server/best-practices-upgrading-zenml.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/steps-pipelines/advanced_features.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/infrastructure-deployment/infrastructure-as-code/best-practices.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/infrastructure-deployment/stack-deployment/register-a-cloud-stack.md
• /home/runner/work/zenml/zenml/scripts/../docs/book/how-to/manage-zenml-server/connecting-to-zenml/README.md

[github-actions]

Documentation Link Check Results

❌ Absolute links check failed
There are broken absolute links in the documentation. See workflow logs for details
❌ Relative links check failed
There are broken relative links in the documentation. See workflow logs for details
_{Last checked: 2025-04-18 08:15:49 UTC}