How To Push a Specific Commit to Remote in Git?

In version control systems like Git, pushing specific commits to a remote repository is a common task. Whether you’re working on a feature branch or fixing a bug, sometimes you need to push only a particular commit without including earlier commits. Here, we’ll explore the steps and commands to Push a Specific Commit to Remote in Git.

Before diving into the steps, it’s essential to grasp the basic concepts:

• Commit: A snapshot of your changes in the repository.
• Branch: A pointer to a specific commit, often representing a line of development.
• Remote: A version of your repository hosted on a server, such as GitHub or GitLab.

There are a few scenarios where you might want to push only a specific commit:

• Feature Isolation: You’re developing a feature and want to share only a stable part of your work.
• Bug Fixes: A critical bug fix needs to be pushed without including other ongoing changes.
• Code Review: Pushing a specific commit for review before merging it into the main branch.

Step 1. Identify the Commit

First, identify the commit hash (SHA) you want to push. You can find this using:

git log

This command lists your commit history. Note the hash of the commit you want to push.

Step 2. Create a New Branch

Create a new branch from the commit you want to push:

git checkout -b new-branch <commit-hash>

Replace <commit-hash> with the hash you identified earlier. This creates a new branch pointing to the specific commit.

Step 3. Push the New Branch

Push the new branch to the remote repository:

git push origin new-branch

This command pushes only the commit(s) in new-branch to the remote repository.

Step 4. Optional: Merge or Rebase

If you eventually want to integrate this commit into another branch (e.g., main), you can either merge or rebase:

Merge

git checkout main
git merge new-branch

Rebase:

git checkout main
git rebase new-branch

Step 5: Cleaning Up

After successfully pushing and integrating the commit, you might want to clean up by deleting the temporary branch:

git branch -d new-branch

If you need to apply a specific commit to another branch without creating a new branch, you can use cherry-pick:

1. Checkout to the Target Branch:

git checkout target-branch

2. Cherry-Pick the Commit:

git cherry-pick <commit-hash>

3. Push the Target Branch:

git push origin target-branch

For more complex scenarios, interactive rebase allows you to re-order, edit, or squash commits:

1. Start Interactive Rebase:

git rebase -i <base-commit>

2. Reorder or Edit Commits:

Follow the instructions in the editor to pick, reword, or squash commits.

3. Complete the Rebase:

git push --force-with-lease

Pushing a specific commit to a remote repository can be essential for maintaining a clean and organized codebase. By creating new branches, using cherry-pick, or leveraging interactive rebase, you can ensure that only the intended changes are shared with your team. Mastering these techniques will enhance your workflow and improve collaboration within your development team.