If the source and target branch for a PR only differ in a single commit then use the commit message and commit description to pre-fill the PR title and PR description.

If the PR has multiple commits use the current technique of computing a PR title based on the branch name. This technique could be slightly improved as well, e.g.

• Branch: <conventional-commit-type>/my-branch-name -> PR title: <conventional-commit-type>: my branch name
• Branch: <conventional-commit-type>-my-branch-name -> PR title: <conventional-commit-type>: my branch name
• Branch: <conventional-commit-type>_my_branch-name -> PR title: <conventional-commit-type>: my branch name
• Branch: wip-my-branch-name -> PR title: [WIP] my branch name
• Branch: wip-<conventional-commit-type>/my-branch-name -> PR title: [WIP] <conventional-commit-type>: my branch name

Basically try to detect WIP and potential conventional commit types in the branch name.

But a priority would be better handling of PRs with just a single commit because I always have to copy the commit information into the PR information when using the squash merge strategy.