4151c3c3a5
* 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>
53 lines
2.0 KiB
YAML
53 lines
2.0 KiB
YAML
name: ✨ Feature Request
|
|
description: Suggest an idea for this project
|
|
labels: ["enhancement", "needs-triage"]
|
|
body:
|
|
- type: textarea
|
|
id: problem-description
|
|
attributes:
|
|
label: What problem is this feature trying to solve?
|
|
description: "A clear and concise description of the problem or user need. Why is this change needed?"
|
|
placeholder: "Currently, I can only use one Gemini tool at a time. I want to be able to chain multiple tools together (e.g., analyze -> codereview -> thinkdeep) in a single workflow."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: proposed-solution
|
|
attributes:
|
|
label: Describe the solution you'd like
|
|
description: A clear and concise description of what you want to happen. How would it work from a user's perspective?
|
|
placeholder: "I'd like to be able to specify a workflow like 'analyze src/ then codereview the findings then use thinkdeep to suggest improvements' in a single command or configuration."
|
|
validations:
|
|
required: true
|
|
|
|
- type: textarea
|
|
id: alternatives
|
|
attributes:
|
|
label: Describe alternatives you've considered
|
|
description: A clear and concise description of any alternative solutions or features you've considered.
|
|
placeholder: "I considered manually running each tool sequentially, but automatic workflow chaining would be more efficient and ensure context is preserved between steps."
|
|
|
|
- type: dropdown
|
|
id: feature-type
|
|
attributes:
|
|
label: Feature Category
|
|
description: What type of enhancement is this?
|
|
options:
|
|
- New tool (chat, codereview, debug, etc.)
|
|
- Workflow improvement
|
|
- Integration enhancement
|
|
- Performance optimization
|
|
- User experience improvement
|
|
- Documentation enhancement
|
|
- Other
|
|
validations:
|
|
required: true
|
|
|
|
- type: checkboxes
|
|
id: contribution
|
|
attributes:
|
|
label: Contribution
|
|
options:
|
|
- label: I am willing to submit a Pull Request to implement this feature.
|
|
|