Git Workflow: Branch Creation, Committing, and Pushing Changes

This guide explains the essential Git workflow used by enterprise developers, focusing on three core steps: creating a branch, committing code, and pushing the branch to a shared remote repository.

1. Create a Branch

Use the git branch command to list branches, git branch <branch-name> to create a new branch, and git checkout <branch-name> to switch to it. You can combine creation and checkout with git checkout -b <branch-name> .

2. Commit Code to the Branch

After editing files (e.g., with code . ), check changes with git status . Stage all modifications using git add --all (or specify files/globs). Commit the staged snapshot with a message: git commit -m "my first git commit" . The commit creates a versioned snapshot of the changes.

3. Push the Branch to the Central Repository

Share your work by pushing the local branch to the remote: git push origin <branch-name> . Team members can then fetch and checkout the branch with git fetch followed by git checkout <branch-name> .

Why Use Branches?

Branches allow developers to isolate experimental changes from the main code line, preventing unstable code from affecting the production or shared environment. Git’s lightweight branches, fast switching, and local operation make them ideal for agile development and collaborative workflows.

Key Advantages of Git Branching

Lightweight creation and deletion without storage overhead.

Instant switching within the same working directory, compatible with IDE debugging.

Fully local operation, enabling independent work without a central server.

Understanding this basic workflow enables developers to start using Git for daily coding tasks, ensuring changes are tracked, versioned, and safely shared with the team.