pr-submitter

To automate GitHub pull request creation, you can use a workflow that pushes your feature branch and generates a validated PR body. This process writes the PR body to a temporary file to avoid shell-escaping issues and creates the pull request via the authenticated gh CLI.

Automated PR body generation breaks due to shell expansion when multi-line strings are passed inline. Writing the bilingual PR body to a temporary file before submission avoids shell-escaping issues and ensures the text is formatted safely.

Yes, you need the gh CLI to create a pull request from a feature branch. The CLI must be properly authenticated before submission, and pre-flight checks verify this authentication status along with ensuring you are not on a protected branch.

Prerequisites for submitting a PR from a non-main branch include having the gh CLI authenticated and ensuring all changes are committed prior to submission. The workflow applies pre-flight checks to verify the current branch is not main and commits are ready.

Yes, you can generate a bilingual PR body for GitHub automatically. The automation supports creating English and Chinese PR bodies, writing the formatted text to a safe temporary file to handle the multi-line content without shell expansion errors.

You should not use an automated PR submission workflow when you are currently on a protected branch like main, or if you have uncommitted changes. The workflow operates within a constrained scope and requires all changes to be committed prior to submission.