Add ddev release port-commit command

[AAraKKe]

What does this PR do?

Adds ddev release port-commit: cherry-picks a commit onto a target branch, pushes a <user>/port-<sha>-to-<target> branch, and opens a PR (ready-for-review by default, --draft to opt in). Preserves .in-toto files from the target branch so package signatures stay intact.

The workflow runs in an isolated git worktree under .worktrees/port-commit/<sanitized-branch>/ so the user's primary working tree is never mutated. On success the worktree is removed; on failure it is left in place and its path is surfaced so the user can inspect or finish the work manually.

Motivation

Brings an existing personal backport script into ddev so the flow is consistent, discoverable, and reuses ddev's git + GitHub helpers.

Implementation notes:

• Worktree-based execution. A SetupWorktreeStep runs git worktree add -B <port-branch> <path> origin/<target> to create the working area; all cherry-pick / .in-toto sweep / commit / push steps run inside a GitRepository instance bound to that worktree. A TeardownWorktreeStep removes the worktree on a clean run, and is intentionally skipped on failure so partial state is recoverable.
• Sequential PortStep workflow. Each step has a uniform describe / planned_commands / execute interface; adding or reordering steps is a one-line change in build_port_steps. --dry-run is centralized in PortStep.run so every step prints its planned commands without executing them.
• Preventive validation. resolve_port_plan fails fast (before any mutation) if github.user is missing, or if github.token is missing while PR creation is enabled (skippable via --no-pr or --dry-run). It also verifies the commit exists, reads its subject, warns about touched .in-toto files, and confirms the resolved plan with the user.
• Async GitHub client. PR creation and label assignment go through AsyncGitHubClient, with httpx.HTTPError / pydantic.ValidationError wrapped into PortStepError so any HTTP / response-shape failure produces a clean abort instead of a raw traceback.

Stacks on top of #23685, which adds the async-client surface and FakeAsyncGitHubClient test helper this PR consumes.

Review checklist (to be filled by reviewers)

• Feature or bugfix MUST have appropriate tests (unit, integration, e2e)
• Add the qa/skip-qa label if the PR doesn't need to be tested during QA.
• If you need to backport this PR to another branch, you can add the backport/<branch-name> label to the PR and it will automatically open a backport PR once this one is merged

[AAraKKe]

• Add ddev release port-commit command #23686 👈 (View in Graphite)
• Restructure github_async into a lazy-loaded package #23685
• master

This stack of pull requests is managed by Graphite. Learn more about stacking.

[chatgpt-codex-connector]

💡 Codex Review

Here are some automated review suggestions for this pull request.

Reviewed commit: 6912a4f767

ℹ️ About Codex in GitHub

Your team has set up Codex to review pull requests in this repo. Reviews are triggered when you

• Open a pull request for review
• Mark a draft as ready
• Comment "@codex review".

If Codex has suggestions, it will comment; otherwise it will react with 👍.

Codex can also answer questions or update the PR. Try commenting "@codex address that feedback".

[chatgpt-codex-connector]

Require a clean index before committing the backport

When the user has staged local edits before running this command, the workflow starts with fetch/checkout/cherry-pick and later runs git commit without ever checking that the index was clean, so those pre-existing staged changes are committed into the backport branch alongside the cherry-pick. This can silently publish unrelated local work in the pushed branch/PR; add an initial clean-worktree/index guard or explicitly reset/abort before the mutating steps.

Useful? React with 👍 / 👎.

[AAraKKe]

Fixed with a validation when creating the plan.

[datadog-datadog-prod-us1]

🎉 All green!

❄️ No new flaky tests detected
🧪 All tests passed

_{This comment will be updated automatically if new data arrives.
🔗 Commit SHA: ca857eb | Docs | Datadog PR Page | Give us feedback!}

[codecov]

Codecov Report

❌ Patch coverage is 96.54655% with 23 lines in your changes missing coverage. Please review.
✅ Project coverage is 90.96%. Comparing base (aeda997) to head (ca857eb).
⚠️ Report is 1 commits behind head on master.

Additional details and impacted files

🚀 New features to boost your workflow:

• ❄️ Test Analytics: Detect flaky tests, report on failures, and find test suite problems.
• 📦 JS Bundle Analysis: Save yourself from yourself by tracking and limiting bundle sizes in JS merges.

Review from NouemanKHAL is dismissed. Related teams and files:

• agent-integrations
  • .gitignore
  • ddev/changelog.d/23686.added
  • ddev/src/ddev/cli/release/init.py
  • ddev/src/ddev/cli/release/port_commit.py
  • ddev/src/ddev/cli/release/port_commit_workflow.py
  • ddev/tests/cli/release/test_port_commit.py

[dd-octo-sts]

Validation Report

All 20 validations passed.

Show details

Validation	Description	Status
agent-reqs	Verify check versions match the Agent requirements file	✅
ci	Validate CI configuration and Codecov settings	✅
codeowners	Validate every integration has a CODEOWNERS entry	✅
config	Validate default configuration files against spec.yaml	✅
dep	Verify dependency pins are consistent and Agent-compatible	✅
http	Validate integrations use the HTTP wrapper correctly	✅
imports	Validate check imports do not use deprecated modules	✅
integration-style	Validate check code style conventions	✅
jmx-metrics	Validate JMX metrics definition files and config	✅
labeler	Validate PR labeler config matches integration directories	✅
legacy-signature	Validate no integration uses the legacy Agent check signature	✅
license-headers	Validate Python files have proper license headers	✅
licenses	Validate third-party license attribution list	✅
metadata	Validate metadata.csv metric definitions	✅
models	Validate configuration data models match spec.yaml	✅
openmetrics	Validate OpenMetrics integrations disable the metric limit	✅
package	Validate Python package metadata and naming	✅
readmes	Validate README files have required sections	✅
saved-views	Validate saved view JSON file structure and fields	✅
version	Validate version consistency between package and changelog	✅

View full run