Thanks for contributing to AutoTeam.
- Clone the repository.
- Install development dependencies:
uv sync --dev- Copy the example environment file if needed:
cp .env.example .env- Update
.envwith your local configuration before running features that depend on CloudMail, CPA, or browser automation.
Run the main local checks before opening a pull request:
uv run ruff check .
uv run ruff format --check .
uv run pytest
uv run python -m compileall -q src/autoteamIf formatting is required:
uv run ruff format .- create feature or fix branches from
dev - keep pull requests focused on a single topic
- prefer small, reviewable commits
Please include:
- a short summary of the problem
- the approach you took
- validation steps you ran locally
- screenshots or log excerpts when UI or browser behavior changes
If your change affects login, sync, quota handling, or Team membership flows, include a brief regression checklist in the PR description.
When adding or changing behavior:
- add or update pytest coverage for the affected logic where possible
- preserve recent regression fixes unless the change intentionally replaces them
- avoid depending on real secrets in tests
- never commit real session tokens, auth files, mailbox credentials, or production
.envvalues - scrub logs and screenshots before sharing them publicly
- follow
SECURITY.mdfor vulnerability reporting
Use short, descriptive commit messages, for example:
fix: guard main account removaltest: cover setup wizard non-interactive flowdocs: clarify Docker startup steps