-
Notifications
You must be signed in to change notification settings - Fork 44.6k
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
refactor(backend): Introduced Graph Input & Output Schema, Merge GraphMeta & Graph, Remove subgraph functionality #8526
Conversation
PR Reviewer Guide 🔍Here are some key observations to aid the review process:
|
This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request. |
…milmajdy/unifygraphmeta-and-graph
Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly. |
If I get more context on the why's of this I can probably give it a go reviewing it but as of now, its probably up to someone else |
This pull request has conflicts with the base branch, please resolve those so we can evaluate the pull request. |
…milmajdy/unifygraphmeta-and-graph
Conflicts have been resolved! 🎉 A maintainer will review the pull request shortly. |
Okay I kinda see where this is going, I can review it later today |
autogpt_platform/backend/migrations/20241103144418_graph_exec_stats_list_to_obj/migration.sql
Show resolved
Hide resolved
Approved with nits |
Background
GraphMeta will require the input & output schema, the information derived from the nodes.
This makes GraphMeta & Graph coincide.
Changes 🏗️
Unrelated change:
Testing 🔍
Note
Only for the new autogpt platform, currently in autogpt_platform/
Configuration Changes 📝
Note
Only for the new autogpt platform, currently in autogpt_platform/
If you're making configuration or infrastructure changes, please remember to check you've updated the related infrastructure code in the autogpt_platform/infra folder.
Examples of such changes might include: