Push Local Branch to Remote Repository in Git

In Git, local and remote repositories work together to manage and collaborate on code. A local repository is a copy of a Git repository that resides on your local machine and a remote repository is a copy of the Git repository hosted on a remote server or a cloud-based service (e.g., GitHub, GitLab, Bitbucket, or a private server).

Pushing your local repository to a remote repository is a fundamental part of using Git, especially when working in a team or on a project that requires collaboration, backup, or version control.

To push a local branch to a remote repository in Git, follow the steps given below.

Check Your Current Branch

Ensure you are on the branch you want to push:

git branch

This will list all local branches; the current branch will be highlighted with an asterisk (*). If you need to switch to a different branch, use:

git checkout <branch-name>

Push the Branch to the Remote Repository

Use the git push command to push the branch to the remote repository:

git push -u origin <branch-name> 

Here, Origin refers to the name of the remote repository, which is usually the default name assigned to the remote. <branch-name> denotes the name of the branch you wish to push. The -u flag establishes the upstream tracking reference, ensuring that future pushes and pulls will automatically use this branch.

Look at the following example -

git push -u origin feature-branch

Verify the Push

You can verify that the branch has been pushed by listing the remote branches:

git branch -r

This will show all branches on the remote repository.

Push Updates to the Branch

After the initial push, you can push further updates to the branch without the -u flag:

git push

Push to a Different Remote

If you have multiple remotes, specify the remote name:

git push -u <remote-name> <branch-name> 

For example,

git push -u upstream feature-branch

Force Push (if necessary)

If you need to overwrite the remote branch (e.g., after rebasing), use the --force flag:

git push --force origin <branch-name> 

Be cautious with force pushing, as it can overwrite changes on the remote.

Pushing your local repository to a remote repository ensures that your code is safe, accessible, and ready for review, testing, and deployment. Whether you're working alone or in a team, pushing to a remote repository is a best practice in modern software development.