graphiti/.github
Daniel Chalef 6a3dce5fd0 Separate database tests from API integration tests
Restructured the workflow into three distinct jobs:

1. unit-tests: Runs on all PRs, no external dependencies (93 tests)
   - No API keys required
   - No database connections required
   - Fast execution

2. database-integration-tests: Runs on all PRs with databases (NEW)
   - Requires Neo4j and FalkorDB services
   - No API keys required
   - Tests database operations without external API calls
   - Includes: test_graphiti_mock.py, test_falkordb_driver.py,
     and utils/maintenance tests

3. api-integration-tests: Runs only for internal contributors
   - Requires API keys (OPENAI_API_KEY, ANTHROPIC_API_KEY, etc.)
   - Conditional execution for same-repo PRs only
   - Tests that make actual API calls to LLM providers

This ensures external contributor PRs can run both unit tests and
database integration tests successfully, while API integration tests
requiring secrets only run for internal contributors.

🤖 Generated with [Claude Code](https://claude.com/claude-code)

Co-Authored-By: Claude <noreply@anthropic.com>
2025-10-11 19:05:15 -07:00
..
ISSUE_TEMPLATE feat: add issue and pull request templates with compliance workflow (#689) 2025-07-08 23:21:26 -07:00
workflows Separate database tests from API integration tests 2025-10-11 19:05:15 -07:00
dependabot.yml migrate to uv (#634) 2025-06-27 12:12:49 -07:00
pull_request_template.md feat: add issue and pull request templates with compliance workflow (#689) 2025-07-08 23:21:26 -07:00
secret_scanning.yml feat: add telemetry with PostHog and update Docker configurations (#633) 2025-06-27 12:23:30 -07:00