Question 1

How do I write good commit messages?

Accepted Answer

Good commit messages: Format: type: brief summary (50 chars max). Types: feat (feature), fix (bug), docs, style, refactor, test, chore. Body: explain why (not how), wrap at 72 chars. Example: feat: Add user authentication. Bad: Fixed stuff, Updated code, changes. Good: fix: Handle null input in validateEmail function. Template: :

[optional body] [optional footer]. Reference issues: Fixes #123. Consistent messages = readable history, easier debugging, better collaboration.

Question 2

Should I commit directly to main branch?

Accepted Answer

Never commit directly to main: Use feature branches for all changes. Reasons: Allows review before merge. Isolated development (doesn't break main). Easy to abandon bad changes. Clear history of what changed. Enables pull request workflow. Exceptions: Minor documentation fixes, urgent hotfixes (still prefer hotfix/ branch). Best practice: Protect main branch (settings require PR for merge). Branch per feature/fix, merge via PR after review. Direct commits = unreviewed code = bugs in production.

Question 3

How do I name Git branches?

Accepted Answer

Branch naming conventions: feature/ - new features (feature/user-auth, feature/payment-flow). bugfix/ - bug fixes (bugfix/login-error). hotfix/ - urgent production fixes (hotfix/security-patch). release/ - release prep (release/v2.0). Rules: Use lowercase, hyphens for spaces. Brief but descriptive. Include issue number if applicable (feature/user-auth-123). Avoid: generic names (my-branch, test), too long (>50 chars), special characters. Consistent naming = organized repo, easier to understand purpose.

Question 4

How often should I commit?

Accepted Answer

Commit frequency: Commit often (every logical change). Ideal: one commit per logical unit (not per line, not per day). Good: fix specific bug = one commit, add feature component = one commit. Bad: huge commits with many unrelated changes, commits with incomplete work. Benefits: Easier review (smaller changes), easier rollback (granular), cleaner history, easier debugging (find exact change). Balance: meaningful commits, not micro-commits. Commit when: logical unit complete, tests pass, not mid-experiment. Frequency = several commits per hour during active work.

Question 5

What should I not commit to Git?

Accepted Answer

Never commit: Secrets/credentials (API keys, passwords, tokens - use .env, secret management). Large binary files (images, videos - use Git LFS or external storage). Generated files (build outputs, node_modules, dist - use .gitignore). IDE config (personal settings - .vscode, .idea individual). Dependencies (package files OK, installed packages NO). Temporary files (logs, cache, temp). Database files (.db, .sqlite). Committing secrets = security breach (keys in history forever). Use .gitignore to exclude properly. Review files before commit.

Version Control Best Practices

Best Practices

Commit Message Format

Branch Naming Strategies

Tips

Git Workflow Checklist