Python Workflow and Delivery

Overview

Branch-to-PR execution discipline for Python work: validate, scope, and ship with confidence. Apply these defaults before opening or updating a PR.

These are preferred defaults for common cases, not universal rules. When deviating, call out tradeoffs and compensating controls (tests, observability, migration, rollback).

When to Use

• Preparing a branch or PR for Python changes.
• CI gate failures on lint, format, or test steps.
• Lockfile or dependency conflicts during uv sync.
• Commits that bundle too many concerns or are hard to review.
• Uncertainty about which validation steps to run before merge.

When NOT to use: