This repository was archived by the owner on Nov 11, 2026. It is now read-only.
Repository navigation
docs: point Agno development to integrations monorepo - #1
Merged
Merged
Conversation
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to subscribe to this conversation on GitHub.
Already have an account?
Sign in.
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
Add a prominent README notice directing Agno integration development and new
issues/pull requests to its directory in
Deepkeepai/deepkeep-integrations.The existing PyPI distribution remains
agno-deepkeep; published 0.1.2 alreadyadvertises the monorepo repository and documentation URLs.
Clarify that the official cookbook example was accepted in agno-agi/agno#9784,
while the separate overview proposal in agno-agi/docs#760 remains open. This does
not create a duplicate upstream submission or claim that the overview is live.
README-only: runtime code, package metadata, installation commands, historical
tags/releases, and repository settings are unchanged. No publication or archival
is performed. The old Publish workflow remains disabled and Test remains active.
Validation
git diff --checkpasses; no runtime code or configuration changes.