nemoclaw-contributor-create-pr

To create a GitHub pull request with DCO sign-off and conventional commits, you need to push your feature branch and generate a PR using the gh CLI. This workflow verifies your branch state, applies a conventional-commits-based title, and includes the DCO sign-off in the structured PR body.

Automating pull request creation with gh CLI requires authenticating the CLI, verifying you are on a feature branch with commits to push, and running pre-PR checks. The process then pushes the branch, generates a formatted PR body, sets assignees, and applies labels.

Yes, gh CLI authentication is a required prerequisite to open a pull request from a feature branch. The automation enforces gh CLI authentication to verify branch state, push commits, and create the PR with proper metadata and labels.

Branch verification before pushing commits for code review ensures you are not on the main branch and confirms there are unpushed commits available. This prevents accidental direct pushes to main and validates that your feature branch has changes ready for a pull request.

Pull request pre-PR checks fail to prevent opening a code review when code quality validation or tests do not pass. This automated step runs before pushing your feature branch to ensure the code meets project guidelines and is ready for review.

The best way to format a PR body according to project guidelines is to use a structured PR template. This automation composes the PR body based on the NemoClaw template, includes DCO sign-off, links related issues, and applies a conventional-commits-based title.