commit-push-hd

To automatically create a missing Git branch before pushing commits, this workflow detects when your current branch is missing or noncompliant and prompts you to create a validly named branch, then proceeds with the commit and push steps.

Git branch naming conventions enforced for feature and hotfix workflows require prefixes like feat/* for standard features and hotfix/* for maintenance, ensuring your branches follow these rules before allowing a push.

Pushing commits to a protected branch triggers pre-push decision logic that validates branch naming and prompts for branch creation or re-naming as needed, guiding the push step while handling any conflicts or push errors.

If your current branch does not match Git naming conventions, the workflow applies branch naming validation and guidance, automatically re-naming or creating a compliant branch like feat/* or hotfix/* before executing the push.

Yes, you can use this workflow for both standard feature and maintenance Git branches, as it handles branch types like feat/* and hotfix/*, enforcing naming rules and guiding the commit and push steps for each.

To handle push errors and conflicts when pushing commits to a remote repository, this workflow includes failure handling that guides you through step-by-step commit and push execution, managing issues during the process.