gh pr create - need help #9517

I used gh repo command in lieu of gh create pr to resolve - however feedback would be appreciated

If repo2 is your fork and you want a PR from david_abc/test_abc:development into orga/test_abc:development, the gh pr create shape is:

gh pr create --repo orga/test_abc --base development --head david_abc:development

That lines up with the current help syntax:

gh pr create --base develop --head monalisa:feature

where:

• --repo is the base repository that will receive the PR
• --base is the target branch in that repository
• --head is <user>:<branch> for the fork branch that contains your changes

So in your case:

• base repo: orga/test_abc
• base branch: development
• head repo owner: david_abc
• head branch: development

If you are already inside the fork checkout on the correct branch and the remote setup is clean, gh pr create --repo orga/test_abc --base development may also be enough interactively, but the explicit form above is the safest for automation.

gh pr create opens your editor for the PR title and body, not for individual commit messages. Commit messages are already fixed when you push the branch.

If you want commit messages in the PR description

Collect them when you push:

# Show commits on this branch vs main
git log main..HEAD --pretty=format:"- %s (%h)"

# Pipe into PR body
gh pr create --title "feat: my change" --body "$(git log main..HEAD --pretty=format:'- %s (%h)')"

If you want to edit commit messages before opening the PR

Use interactive rebase before gh pr create:

git rebase -i main
# mark commits as 'reword', save, edit each message
git push --force-with-lease
gh pr create

If the editor opens but feels empty

Set your editor explicitly:

gh config set editor "code --wait"   # VS Code
# or
$env:EDITOR = "notepad"              # PowerShell session

Common mistake on Windows

Running gh pr create in PowerShell without $env:EDITOR set may fall back to a minimal editor. Setting gh config set editor fixes it permanently.