commit-push-pr

To automate your git workflow, you can stage changes, generate conventional commits, push to origin, and open a pull request using the gh CLI. This process handles feature work, bug fixes, and documentation updates while enforcing pre-commit hooks.

Conventional commits provide a standardized format for commit messages. This automation enforces conventional commit formats during the staging and committing process, ensuring consistent git history across your repository without requiring manual message formatting.

Pre-commit hooks are strictly enforced during the commit process to maintain code quality. You can only skip pre-commit hooks by explicitly passing a designated flag, preventing accidental bypasses of your repository's configured quality checks.

Yes, the git workflow explicitly handles edge cases like having no changes to commit or missing an upstream branch. It safely manages upstream tracking during the push operation and aborts gracefully when there are no staged modifications.

After pushing your branch to origin, the workflow uses the gh CLI to safely create a pull request. This automated PR creation occurs directly after the push step, linking your newly pushed branch to the target repository.

The best way to manage git workflows for bug fixes and feature work is automating the end-to-end sequence. Staging changes, applying conventional commits, enforcing pre-commit hooks, and opening PRs reduces manual errors and standardizes repository contributions.