* Migration from docker to standalone server Migration handling Fixed tests Use simpler in-memory storage Support for concurrent logging to disk Simplified direct connections to localhost * Migration from docker / redis to standalone script Updated tests Updated run script Fixed requirements Use dotenv Ask if user would like to install MCP in Claude Desktop once Updated docs * More cleanup and references to docker removed * Cleanup * Comments * Fixed tests * Fix GitHub Actions workflow for standalone Python architecture - Install requirements-dev.txt for pytest and testing dependencies - Remove Docker setup from simulation tests (now standalone) - Simplify linting job to use requirements-dev.txt - Update simulation tests to run directly without Docker Fixes unit test failures in CI due to missing pytest dependency. 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Remove simulation tests from GitHub Actions - Removed simulation-tests job that makes real API calls - Keep only unit tests (mocked, no API costs) and linting - Simulation tests should be run manually with real API keys - Reduces CI costs and complexity GitHub Actions now only runs: - Unit tests (569 tests, all mocked) - Code quality checks (ruff, black) 🤖 Generated with [Claude Code](https://claude.ai/code) Co-Authored-By: Claude <noreply@anthropic.com> * Fixed tests * Fixed tests --------- Co-authored-by: Claude <noreply@anthropic.com>
61 lines
1.8 KiB
YAML
61 lines
1.8 KiB
YAML
name: 📖 Documentation Improvement
|
|
description: Report an issue or suggest an improvement for the documentation
|
|
labels: ["documentation", "good first issue"]
|
|
body:
|
|
- type: input
|
|
id: location
|
|
attributes:
|
|
label: Documentation Location
|
|
description: "Which file or page has the issue? (e.g., README.md, CONTRIBUTING.md, CLAUDE.md)"
|
|
placeholder: "e.g., README.md"
|
|
validations:
|
|
required: true
|
|
|
|
- type: dropdown
|
|
id: issue-type
|
|
attributes:
|
|
label: Type of Documentation Issue
|
|
description: What kind of documentation improvement is this?
|
|
options:
|
|
- Typo or grammar error
|
|
- Unclear or confusing explanation
|
|
- Outdated information
|
|
- Missing information
|
|
- Code example doesn't work
|
|
- Installation/setup instructions unclear
|
|
- Tool usage examples need improvement
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: problem
|
|
attributes:
|
|
label: What is wrong with the documentation?
|
|
description: "Please describe the problem. Be specific about what is unclear, incorrect, or missing."
|
|
placeholder: "README is missing some details"
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: suggestion
|
|
attributes:
|
|
label: Suggested Improvement
|
|
description: "How can we make it better? If you can, please provide the exact text or changes you'd like to see."
|
|
placeholder: "Please improve...."
|
|
|
|
|
|
- type: dropdown
|
|
id: audience
|
|
attributes:
|
|
label: Target Audience
|
|
description: Which audience would benefit most from this improvement?
|
|
options:
|
|
- New users (first-time setup)
|
|
- Developers (contributing to the project)
|
|
- Advanced users (complex workflows)
|
|
- All users
|
|
validations:
|
|
required: true
|
|
|