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

📚Ppipelines how-to guide #2109

Conversation

ashwinvaidya17
Copy link
Collaborator

📝 Description

  • Add tutorial for pipelines

✨ Changes

Select what type of change your PR is:

  • 🐞 Bug fix (non-breaking change which fixes an issue)
  • 🔨 Refactor (non-breaking change which refactors the code base)
  • 🚀 New feature (non-breaking change which adds functionality)
  • 💥 Breaking change (fix or feature that would cause existing functionality to not work as expected)
  • 📚 Documentation update
  • 🔒 Security update

✅ Checklist

Before you submit your pull request, please make sure you have completed the following steps:

  • 📋 I have summarized my changes in the CHANGELOG and followed the guidelines for my type of change (skip for minor changes, documentation updates, and test enhancements).
  • 📚 I have made the necessary updates to the documentation (if applicable).
  • 🧪 I have written tests that support my changes and prove that my fix is effective or my feature works (if applicable).

For more information about code review checklists, see the Code Review Checklist.

samet-akcay and others added 6 commits May 24, 2024 14:26
Signed-off-by: Ashwin Vaidya <ashwinnitinvaidya@gmail.com>
Add reference guide

Signed-off-by: Ashwin Vaidya <ashwinnitinvaidya@gmail.com>
Signed-off-by: Ashwin Vaidya <ashwinnitinvaidya@gmail.com>
Copy link
Contributor

@blaz-r blaz-r left a comment

Choose a reason for hiding this comment

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

I have used this as a guide for tiled ensemble refactoring. It's nice and concise, uses a simple example that demonstrates everything that one should need to know about pipelines.
So content-wise this looks great to me.

@ashwinvaidya17 ashwinvaidya17 merged commit c3e0b38 into openvinotoolkit:main Jul 1, 2024
1 of 4 checks passed
@ashwinvaidya17 ashwinvaidya17 deleted the docs/pipelines_how_to_guide branch July 1, 2024 12:00
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
None yet
Development

Successfully merging this pull request may close these issues.

None yet

3 participants