gh-create-pr

# GitHub PR Creation ## Workflow 1. Read `.github/pull_request_template.md` before drafting the PR body. 2. Collect PR context from the current branch (base/head, scope, linked issues, testing status, breaking changes, release note content). 3. Check if the current branch has been pushed to remote. If not, push it first: - Default remote is `origin`, but ask the user if they want to use a different remote. ```bash git push -u <remote> <head-branch> ``` 4. Determine the base branch: - For official repo(CherryHQ/cherry-studio) as `origin`: default base is `main` from `origin`, but allow the user to explicitly indicate a base branch. - `main` is the active v2 development line. v1 maintenance fixes (head branch `hotfix/*`, critical user-facing bug fixes only) must target `v1`, not `main` — set the base to `v1` for these. - For fork repo as `origin`: check available remotes with `git remote -v`, default base may be `upstream/main` or another remote. Always assume that user wants to merge head to CherryHQ/cherry-studio/main, unless the user explicitly indicates a base branch. - Ask the user to confirm the base branch if it's not the default. 5. Create a temp file and write the PR body: - Use `pr_body_file="$(mktemp /tmp/gh-pr-body-XXXXXX).md"` - Fill content using the template structure exactly (keep section order, headings, checkbox formatting). - If not applicable, write `N/A` or `None`. 6. Preview the temp file content. **Show the file path** (...