raise-pull-request

You are an expert at creating pull requests for the Home Assistant core repository. You will automate the PR creation process with proper verification, formatting, testing, and checkbox handling.

Execute each step in order. Do not skip steps.

Step 1: Gather Information

Run these commands in parallel to analyze the changes:

# Get current branch and remote
git branch --show-current
git remote -v | grep push

# Determine the best available dev reference
if git rev-parse --verify --quiet upstream/dev >/dev/null; then
  BASE_REF="upstream/dev"
elif git rev-parse --verify --quiet origin/dev >/dev/null; then
  BASE_REF="origin/dev"
elif git rev-parse --verify --quiet dev >/dev/null; then
  BASE_REF="dev"
else
  echo "Could not find upstream/dev, origin/dev, or local dev"
  exit 1
fi

BASE_SHA="$(git merge-base "$BASE_REF" HEAD)"
echo "BASE_REF=$BASE_REF"
echo "BASE_SHA=$BASE_SHA"

# Get commit info for this branch vs dev
git log "${BASE_SHA}..HEAD" --oneline

# Check what files changed
git diff "${BASE_SHA}..HEAD" --name-only

# Check if test files were added/modified
git diff "${BASE_SHA}..HEAD" --name-only | grep -E "^tests/.*\.py$" || echo "NO_TESTS_CHANGED"

# Check if manifest.json changed
git diff "${BASE_SHA}..HEAD" --name-only | grep "manifest.json" || echo "NO_MANIFEST_CHANGED"

From the file paths, extract the integration domain from homeassistant/components/{integration}/ or tests/components/{integration}/.

Track results:

• BASE_REF: the dev reference used for comparison
• BASE_SHA: the merge-base commit used for diff-based checks
• TESTS_CHANGED: true if test files were added or modified
• MANIFEST_CHANGED: true if manifest.json was modified

If no suitable dev reference is available, STOP and tell the user to fetch upstream/dev, origin/dev, or a local dev branch before continuing.

Step 2: Run Code Quality Checks

Run prek to perform code quality checks (formatting, linting, hassfest, etc.) on the files changed since BASE_SHA: