https://github.com/topoteretes/cognee
Memory for AI Agents in 5 lines of code
https://github.com/topoteretes/cognee
ai ai-agents ai-memory cognitive-architecture cognitive-memory contributions-welcome good-first-issue good-first-pr graph-database graph-rag graphrag help-wanted knowledge knowledge-graph neo4j open-source openai rag vector-database
Last synced: 3 days ago
JSON representation
Memory for AI Agents in 5 lines of code
- Host: GitHub
- URL: https://github.com/topoteretes/cognee
- Owner: topoteretes
- License: apache-2.0
- Created: 2023-08-16T16:16:33.000Z (over 1 year ago)
- Default Branch: main
- Last Pushed: 2025-05-13T15:24:56.000Z (3 days ago)
- Last Synced: 2025-05-13T15:48:17.940Z (3 days ago)
- Topics: ai, ai-agents, ai-memory, cognitive-architecture, cognitive-memory, contributions-welcome, good-first-issue, good-first-pr, graph-database, graph-rag, graphrag, help-wanted, knowledge, knowledge-graph, neo4j, open-source, openai, rag, vector-database
- Language: Jupyter Notebook
- Homepage: https://www.cognee.ai
- Size: 83.6 MB
- Stars: 2,126
- Watchers: 14
- Forks: 193
- Open Issues: 36
-
Metadata Files:
- Readme: .github/README_WORKFLOW_MIGRATION.md
- Contributing: CONTRIBUTING.md
- License: LICENSE
- Code of conduct: CODE_OF_CONDUCT.md
Awesome Lists containing this project
- StarryDivineSky - topoteretes/cognee
- awesome-ChatGPT-repositories - cognee - Memory management for the AI Applications and AI Agents (Openai)
- awesome_ai_agents - Cognee - Cognee is an open-source framework aimed at simplifying data processing for large language models (LLMs) by creating knowledge graphs and data models, offering tools for information addition, knowledge creation, and similarity-based search [github](https://github.com/topoteretes/cognee) (Learning / Repositories)
- awesome_ai_agents - Cognee - Cognee is an open-source framework aimed at simplifying data processing for large language models (LLMs) by creating knowledge graphs and data models, offering tools for information addition, knowledge creation, and similarity-based search [github](https://github.com/topoteretes/cognee) (Learning / Repositories)
- awesome-safety-critical-ai - `topoteretes/cognee`
README
# Workflow Migration to Test Suites
This document explains how to ensure all test workflows are only run through the central test-suites.yml workflow.
## Why Migrate to Test Suites?
1. **Prevent Duplicate Runs**: Avoid running the same tests multiple times
2. **Sequential Execution**: Ensure tests run in the correct order
3. **Centralized Control**: Manage all tests from a single place
4. **Resource Efficiency**: Run tests only when needed
## Automated Migration
We've provided a script to automatically convert individual workflows to only run when called by the test-suites.yml file:
```bash
# Make the script executable
chmod +x .github/workflows/disable_independent_workflows.sh
# Run the script
.github/workflows/disable_independent_workflows.sh
```
## Manual Migration
For each workflow file that should only run through test-suites.yml:
1. Open the workflow file
2. Find the `on:` section, which typically looks like:
```yaml
on:
workflow_dispatch:
pull_request:
types: [labeled, synchronize]
```
3. Replace it with:
```yaml
on:
workflow_call:
secrets:
inherit: true
```
4. Save the file
## Verification
After modifying the workflows, verify that:
1. The workflows no longer trigger on pushes or PRs
2. The workflows still run correctly when called by test-suites.yml
3. No tests are left out of the test-suites.yml orchestrator
## Example Conversion
**Before:**
```yaml
name: test | chromadb
on:
workflow_dispatch:
pull_request:
types: [labeled, synchronize]
concurrency:
group: ${{ github.workflow }}-${{ github.event.pull_request.number || github.ref }}
cancel-in-progress: false
jobs:
run_chromadb_integration_test:
name: chromadb test
runs-on: ubuntu-22.04
# ...rest of workflow...
```
**After:**
```yaml
name: test | chromadb
on:
workflow_call:
secrets:
inherit: true
jobs:
run_chromadb_integration_test:
name: chromadb test
runs-on: ubuntu-22.04
# ...rest of workflow...
```
## Special Cases
- **CI/CD Workflows**: Don't modify workflows for CI/CD pipelines like cd.yaml and cd_prd.yaml
- **Shared Workflows**: Keep reusable_*.yml workflows as they are, since they're already designed to be called by other workflows
- **Infrastructure Workflows**: Don't modify workflows that handle infrastructure or deployments