github-pr-workflow

Push your branch with git push -u origin HEAD, then run gh pr create with a title and body. Without the gh CLI, send a POST request to the GitHub API pulls endpoint with your token, head branch, and base branch.

Fetch the failed run logs with gh run view --log-failed or the API logs endpoint, identify the error pattern (test, lint, type, or build failure), patch the code, commit, push, and re-check status. Repeat up to three attempts before asking the user.

Yes, every operation has a git plus curl fallback using the GitHub REST API with a GITHUB_TOKEN. This covers PR creation, status checks, log downloads, merging, and even auto-merge via the GraphQL API.

Run gh pr checks or gh pr checks --watch to poll until completion. With curl, query the commits status endpoint and check-runs endpoint for the branch HEAD SHA, optionally looping every 30 seconds until the state resolves.

It follows Conventional Commits: type(scope): description, with types like feat, fix, refactor, docs, test, ci, chore, and perf. Bodies wrap at 72 characters and can link issues with Closes #42 or mark breaking changes with an exclamation mark.

Permission failures usually mean the workflow lacks required token scopes or secrets are missing. Add a permissions block to the workflow YAML, verify secrets exist in repo settings, and note that fork PRs cannot access some secrets by design.