1k-create-pr

Automating pull request creation for a monorepo involves detecting the correct base branch, running lint fixes, staging commits with conventional messages, and pushing to remote to open a PR. The workflow enforces PR titling with OK- IDs and an English body template for project compliance.

Auto-detecting the base branch in a git workflow requires analyzing the repository structure to determine the correct integration target. The automation then creates feature branches, stages commits, and pushes to remote to ensure PRs target the correct base.

Generating a PR body with context involves extracting conversation history to enrich the title and body, aligning with project standards and OK-{number} references. This ensures high-quality PRs with descriptive English body templates generated from contextual summaries.

Running lint fixes and committing changes in a single automated git workflow is possible by staging files, applying lint corrections, and creating conventional commit messages sequentially. This end-to-end process prevents human error and ensures code style compliance before pushing to remote.

Yes, this PR automation workflow enforces conventional commit messages by automatically staging changes and committing them with standardized formats. It also enforces PR titling with OK- IDs and an English PR body template to maintain monorepo project standards.

You need an automated workflow for OneKey app-monorepo pull requests to reduce manual steps and potential human error. It ensures correct base selection, applies lint fixes, and generates high-quality PRs with contextual summaries and OK-{number} references via a single command.