Map all author variations to Daniel Wagner <dw@danieljw.net>:
- daniel <daniel@hp.k8sx.com>
- Daniel <dw@danieljw.net>
- Daniel Wagner <daniel.wagner89@gmail.com>
This ensures consistent author attribution across all commits.
The mailmap is used by GitHub and git tools for display.
- Add Initial Setup section with uv installation and venv creation steps
- Include pre-commit hook setup with clear explanation of automation
- Update Code Style section to mention pre-commit auto-fixing
- Update Running Tests Locally with venv activation and linting commands
- Add note clarifying pre-commit integration in CI/CD workflow
This ensures new developers/agents know how to:
1. Install dependencies properly with uv
2. Set up pre-commit for automatic linting and testing
3. Run tests and linting commands manually when needed
- Replace deprecated class Config pattern with model_config = ConfigDict(...)
- Add ConfigDict import from pydantic
- Fixes PydanticDeprecatedSince20 warning in test output
- Maintains all existing functionality
All 73 tests pass without warnings.
- Add astral-sh/ruff-pre-commit as official ruff hook
- Enable ruff with --fix for automatic linting fixes
- Add ruff-format for code formatting
- Keep pytest hook for test running
Now pre-commit will automatically fix linting issues and run tests before commits.
- Add .pre-commit-config.yaml with hooks for ruff check and pytest
- Expand README with quick start guide and development instructions
- Include pre-commit setup instructions
- Add references to AGENTS.md and CONFIGURATION.md
To use pre-commit:
pip install pre-commit
pre-commit install
Hooks run automatically on commit (ruff check + pytest).
- Add tests/conftest.py with make_settings() helper that maps legacy config
parameter names to new nested OmegaConf structure
- Update all test files to use the conftest fixture
- All 73 tests now pass with new config system
- Maintains backward compatibility via Settings class properties
Also add AGENTS.md with comprehensive AI agent guidelines:
- Project overview and key technologies
- Directory structure reference
- Development workflow and common tasks
- Testing strategy and patterns
- CI/CD pipeline overview
- Common pitfalls and best practices
- Debugging guide for agents working on the project
Only include the 4 required environment variables:
- STEWARD__TELEGRAM__BOT_TOKEN
- STEWARD__OPENAI__API_KEY
- STEWARD__TELEGRAM__ALLOWED_USER_IDS
- STEWARD__TELEGRAM__GROUP_IDS
All other settings have sensible defaults in config_schema.yaml and can be
overridden if needed. This keeps the example file clean and focused.
Configuration changes:
- Replace pydantic-settings with OmegaConf for flexible config management
- Support YAML config files via CONFIG_FILE environment variable
- Support environment variables with STEWARD__SECTION__KEY format
- Add config_schema.yaml as default configuration schema
- Create pydantic models for each configuration section for type safety
- Maintain backward compatibility via properties on Settings class
- Add CONFIGURATION.md with comprehensive setup and usage guide
- Update pyproject.toml to include config_schema.yaml in package data
Build/deployment changes:
- Replace pip with uv in Dockerfile for faster dependency installation
- Create docker-compose.dev.yml for local development (build .)
- Keep docker-compose.yml for production (uses ghcr.io/djw4/steward:latest)
- Update .env.example with new STEWARD__* variable format
This setup is designed for Kubernetes deployment:
- Non-sensitive config goes in ConfigMap (config.yaml)
- Secrets go in Secret resources (environment variables)
- Single unified configuration system for all environments
- Add TELEGRAM_GROUP_IDS configuration setting to enable optional group/channel filtering
- Add _is_group_enabled() authorization check to all command handlers
- Add group/channel authorization check to message_handler
- All handlers now verify both user authorization and group authorization
- If TELEGRAM_GROUP_IDS is not configured, bot accepts messages from any group
- If TELEGRAM_GROUP_IDS is configured, bot only processes messages from those groups
This enables the bot to be used in group chats and channels with Topics/Threads support.
