commit-push

To safely commit and push code, this workflow blocks direct commits to main branches like main, master, and dev, prompting you to create a new branch instead. This ensures changes are safely integrated without violating branch protection rules.

The best way to write a git commit message is to explain the "why" behind your changes, not just the "what". This practice ensures your code changes are well-documented, atomic, and independently trackable in version control.

To handle pre-commit hook failures without amending, fix the issues and create a completely new commit. This ensures your git history remains clean and never alters existing commits when resolving pre-commit hook errors.

Yes, you can squash or interactively rebase staged changes before pushing, but only when explicitly requested. By default, the git workflow creates new commits to keep your repository history atomic and independently reversible.

You should create separate commits for a new feature and a bug fix to ensure each change is independently trackable and reversible. This strategic committing approach keeps your version control history clean and well-documented.