Skip to main content
March 23, 2026Dan Rodney/2 min read

Git Setup: Your Name & Email

Essential Git configuration for professional development workflows

Why Git Configuration Matters

Proper Git configuration ensures accountability and communication in collaborative development environments by tracking who made changes and how to contact them.

Essential Git Configuration Elements

User Name

Identifies you in commit history and collaboration logs. Should match your professional identity for team recognition.

Email Address

Links commits to your identity and enables communication. Often integrates with platforms like GitHub for profile matching.

Setting up Git

Git is essential for collaborative development in any professional environment. To maintain proper attribution and enable seamless team communication, Git requires your identity configuration before you can begin committing code. This setup ensures that every change you make is properly tracked and attributed to you across all repositories.

Platform-Specific Terminal Access

1

Mac Users

Navigate to Applications folder, then Utilities subfolder, and open Terminal.app to access the command line interface.

2

Windows Users

Launch Git Bash application, typically found as desktop icon or in Windows Start menu within a Git folder.

Git Bash vs Command Prompt

Windows users should use Git Bash rather than Command Prompt as it provides a Unix-like environment with proper Git command support.

Tell Git Your Name & Email

  1. First, access your command line interface. The process varies by operating system:

    • Mac: Navigate to Applications > Utilities and launch Terminal.app. Alternatively, press Cmd + Space and search for "Terminal".
    • Windows: Open the Git Bash application, which you'll find either as a desktop shortcut or in your Start menu under the Git program folder. This provides a Unix-like terminal optimized for Git operations.

  2. Configure your name by entering the following command. Replace Your Name with your actual first and last name, keeping the quotation marks intact:

    git config --global user.name "Your Name"

  3. Set your email address with this command, substituting you@example.com with your professional email address while preserving the quotes:

    git config --global user.email "you@example.com"

Remember that these configuration changes apply only to future commits. Any existing commits in your repositories will retain their original author information, ensuring the integrity of your project's history.

Git Global Configuration Commands

1

Set Your Name

Run 'git config --global user.name "Your Name"' replacing Your Name with your actual first and last name while keeping the quotes.

2

Set Your Email

Run 'git config --global user.email "you@example.com"' replacing the email with your actual address while keeping the quotes.

Configuration Timing Impact

Changes to name and email settings only affect future commits and work. Previous commits retain the configuration that was active when they were created.

Global vs Local Configuration

Global Configuration

Applied to all repositories on your system. Uses the --global flag and affects your entire development environment.

Repository-Specific

Can be set per project without --global flag. Useful when contributing to different projects with different identities.

Checking Your Git Setup (Name & Email)

To verify your current Git configuration or troubleshoot setup issues, you can query your existing settings using the same commands without providing new values. Simply run these commands to display your current configuration:

git config --global user.name
git config --global user.email

Verification Commands

1

Check Name Setting

Run 'git config --global user.name' without quotes or values to display currently configured name.

2

Check Email Setting

Run 'git config --global user.email' without quotes or values to display currently configured email address.

Git Configuration Verification Checklist

0/3
Configuration Complete

With name and email properly configured, Git will now correctly attribute your contributions in collaborative development environments.

Key Takeaways

1Git requires user name and email configuration for proper attribution in collaborative development environments
2Configuration setup varies by platform: Mac users access Terminal.app while Windows users launch Git Bash application
3Global configuration commands use --global flag and affect all repositories on your development system
4Name and email changes only impact future commits, not previously created work or commit history
5Verification commands run the same configuration commands without providing values to check current settings
6Proper Git configuration enables accountability and communication channels in team development workflows
7Repository-specific configuration can override global settings for project-specific identity requirements
8Testing configuration with sample commits validates that settings are correctly applied to Git operations

RELATED ARTICLES