Create Pull Request

Publish the completed change as one accurate GitHub pull request that is ready for review.

A request to open the PR authorizes creating a branch when needed, committing the in-scope changes, pushing without force, and creating the PR or updating a matching open one. Do these without pausing to confirm them. The request does not authorize merging, auto-merge, force-pushing, history rewrites, labels, reviewers, assignees, issue edits, or touching unrelated changes.

Stop and report only when:

• the change is empty, incomplete, or mixed with changes whose ownership is unclear
• a required check fails or cannot run
• publishing fails

1. Establish the change

• Read the repository instructions, the source issue if there is one, and a few recent commits to learn the repository's conventions.
• The head is the current branch unless the user names one. The base is the branch the user or repository instructions name, otherwise the repository's default branch. If the head is the base branch or HEAD is detached, create a branch named for the change.
• Review the full diff from the merge base with the base branch, plus staged, unstaged, and untracked changes. Stage only paths that belong to this change. Never stash, reset, clean, amend, or rebase to make publishing work.
• If an open PR from this head to this base exists, update it instead of creating another.