Files
micro--go-micro/contrib/langchain-go-micro/CONTRIBUTING.md
T
wehub-resource-sync e071084ebe
govulncheck / govulncheck (push) Has been cancelled
Lint / golangci-lint (push) Has been cancelled
Run Tests / Unit Tests (push) Has been cancelled
Run Tests / Etcd Integration Tests (push) Has been cancelled
Harness (E2E) / Harnesses (mock LLM) (push) Has been cancelled
Harness (E2E) / Provider harnesses (live LLM conformance) (push) Has been cancelled
chore: import upstream snapshot with attribution
2026-07-13 12:40:33 +08:00

2.0 KiB

Contributing to LangChain Go Micro

Thank you for your interest in contributing to the LangChain Go Micro integration!

Development Setup

  1. Clone the repository:
git clone https://github.com/micro/go-micro
cd go-micro/contrib/langchain-go-micro
  1. Create a virtual environment:
python -m venv venv
source venv/bin/activate  # On Windows: venv\Scripts\activate
  1. Install in development mode:
pip install -e ".[dev]"

Running Tests

Run all tests:

pytest

Run with coverage:

pytest --cov=langchain_go_micro --cov-report=html

Run specific tests:

pytest tests/test_toolkit.py::TestGoMicroToolkit::test_get_tools

Code Style

We use several tools to maintain code quality:

Black (code formatting)

black langchain_go_micro tests examples

MyPy (type checking)

mypy langchain_go_micro

Ruff (linting)

ruff check langchain_go_micro tests

Run all checks:

black langchain_go_micro tests examples && \
mypy langchain_go_micro && \
ruff check langchain_go_micro tests

Testing with Real Services

To test with real Go Micro services:

  1. Start example services:
cd ../../examples/mcp/documented
go run main.go
  1. Run integration tests:
cd contrib/langchain-go-micro
pytest tests/integration/ -v

Submitting Changes

  1. Fork the repository
  2. Create a feature branch (git checkout -b feature/my-feature)
  3. Make your changes
  4. Run tests and code quality checks
  5. Commit your changes (git commit -am 'Add new feature')
  6. Push to your fork (git push origin feature/my-feature)
  7. Create a Pull Request

Pull Request Guidelines

  • Include tests for new features
  • Update documentation as needed
  • Follow existing code style
  • Add entry to CHANGELOG.md
  • Ensure all tests pass
  • Keep changes focused and atomic

Questions?