-
Notifications
You must be signed in to change notification settings - Fork 672
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
[Docs] Document protocol used by Flyte CoPilot #317
Comments
The design for flyte copilot is available here. this should be converted to the documentation |
@SandraGH5 FYI |
* Start-Node outputUri copied in input and output result Signed-off-by: Prafulla Mahindrakar <[email protected]> * Test fix Signed-off-by: Prafulla Mahindrakar <[email protected]> * Linter fix Signed-off-by: Prafulla Mahindrakar <[email protected]> * Incorporated the feedback Signed-off-by: Prafulla Mahindrakar <[email protected]> * Only adding outputUri in the result for start-node Signed-off-by: Prafulla Mahindrakar <[email protected]> * linter issues Signed-off-by: Prafulla Mahindrakar <[email protected]>
Signed-off-by: Yuvraj <[email protected]>
Signed-off-by: Prafulla Mahindrakar <[email protected]>
* Start-Node outputUri copied in input and output result Signed-off-by: Prafulla Mahindrakar <[email protected]> * Test fix Signed-off-by: Prafulla Mahindrakar <[email protected]> * Linter fix Signed-off-by: Prafulla Mahindrakar <[email protected]> * Incorporated the feedback Signed-off-by: Prafulla Mahindrakar <[email protected]> * Only adding outputUri in the result for start-node Signed-off-by: Prafulla Mahindrakar <[email protected]> * linter issues Signed-off-by: Prafulla Mahindrakar <[email protected]>
Hello 👋, This issue has been inactive for over 9 months. To help maintain a clean and focused backlog, we'll be marking this issue as stale and will close the issue if we detect no activity in the next 7 days. Thank you for your contribution and understanding! 🙏 |
Hello 👋, This issue has been inactive for over 9 months and hasn't received any updates since it was marked as stale. We'll be closing this issue for now, but if you believe this issue is still relevant, please feel free to reopen it. Thank you for your contribution and understanding! 🙏 |
Signed-off-by: Prafulla Mahindrakar <[email protected]>
Signed-off-by: Prafulla Mahindrakar <[email protected]>
Is this still a need? Also the referenced design doc is not accesible |
Signed-off-by: Prafulla Mahindrakar <[email protected]>
Motivation: Why do you think this is important?
When new users are using CoPilot, the protocol used to communicate should be clearly documented.
Goal: What should the final outcome look like, ideally?
Any user should be able to refer to this documentation and use coPilot
Describe alternatives you've considered
NA
Flyte component
[Optional] Propose: Link/Inline
NA
Additional context
NA
Is this a blocker for you to adopt Flyte
This is a blocker to use CoPilot
The text was updated successfully, but these errors were encountered: