[Tracking] pr/issue create ux improvements

[vilmibm]

The UX of pr create and to a lesser extent issue create is confusing, complex, and leads to a lot of confusion and opened issues.

This tracking issue is for collecting issues related to the UX of these commands and for making a plan of how to improve them.

It's possible we will want to incorporate these changes into a 3.0 release.

issue create

• non-interactive issue create with template #7405
• Add issue create --editor #7193

issue edit

• Unable to assign issues to myself via --add-assignee @me or --add-assignee USERNAME #6235

pr create

• gh pr create --fill fails with confusing error: could not compute title or body defaults: fatal: ambiguous argument  #5896
• 'gh pr create' fails if skipping pushing with "GraphQL error: Head sha can't be blank, Base sha can't be blank, No commits between master and <branch>, Head ref must be a branch" #2691
• gh pr create Add option to use first commit as PR title/description #7239
  • Feature: Add fill-first flag to pr create command #7398
• Selecting assignees interactively when submitting a pull request #5866
• gh pr create: Put constituent commit messages as comments in the body #8018
• gh pr create --fill-from and --fill-latest arguments #8163
• pr create: flag to push local branch to remote without prompting #8152

pr edit

• gh pr edit --add-reviewer Don't acquire organizational teams if it's not necessary #4844
  • issue edit: avoid race conditions when editing assignees, reviewers #4876
• https://github.com/github/cli/issues/125
• gh pr edit does not work with only pull-requests: write permissions #6274
• Editing a pr with add-reviewer and and empty string causes all reviewers to be removed. #7721

[ElijahLynn]

Hi, thanks for creating this. Can you also create and track an issue for Discussion
#8631, "How to gh pr create --custom-field with GitHub Projects Beta (v2)?".

[qrilka]

Are there any plans for for the --fill option to use full commit messages instead of just taking first lines?