In Git, the term remote is concerned with the remote repository. It is a shared repository that all team members use to exchange their changes. A remote repository is stored on a code hosting service like an internal server, GitHub, Subversion, and more. In the case of a local repository, a remote typically does not provide a file tree of the project’s current state; as an alternative, it only consists of the .git versioning data.
The developers can perform many operations with the remote server. These operations can be a clone, fetch, push, pull, and more. Consider the below image:

Check your Remote

To check the configuration of the remote server, run the git remote command. The git remote command allows accessing the connection between remote and local. If you want to see the original existence of your cloned repository, use the git remote command. It can be used as:
Syntax:
1. $ git remote
Output:

The given command is providing the remote name as the origin. Origin is the default name for the remote server, which is given by Git.
Git remote -v:
Git remote supports a specific option -v to show the URLs that Git has stored as a short name. These short names are used during the reading and write operation. Here, -v stands for verbose. We can use –verbose in place of -v. It is used as:
Syntax:
1. $ git remote -v
Or
1. $ git remote –verbose
Output:

The above output is providing available remote connections. If a repository contains more than one remote connection, this command will list them all.

Git Remote Add

When we fetch a repository implicitly, git adds a remote for the repository. Also, we can explicitly add a remote for a repository. We can add a remote as a shot nickname or short name. To add remote as a short name, follow the below command:
Syntax:
1. $ git remote add <short name><remote URL>
Output:

In the above output, I have added a remote repository with an existing repository as a short name “hd”. Now, you can use “hd” on the command line in place of the whole URL. For example, you want to pull the repository, consider below output:

I have pulled a repository using its short name instead of its remote URL. Now, the repository master branch can be accessed through a short name.

Fetching and Pulling Remote Branch

You can fetch and pull data from the remote repository. The fetch and pull command goes out to that remote server, and fetch all the data from that remote project that you don’t have yet. These commands let us fetch the references to all the branches from that remote.
To fetch the data from your remote projects, run the below command:
1. $ git fetch <remote>
To clone the remote repository from your remote projects, run the below command:
1. $ git clone<remote>
When we clone a repository, the remote repository is added by a default name “origin.” So, mostly, the command is used as git fetch origin.
The git fetch origin fetches the updates that have been made to the remote server since you cloned it. The git fetch command only downloads the data to the local repository; it doesn’t merge or modify the data until you don’t operate. You have to merge it manually into your repository when you want.
To pull the repository, run the below command:
1. $ git pull <remote>
The git pull command automatically fetches and then merges the remote data into your current branch. Pulling is an easier and comfortable workflow than fetching. Because the git clone command sets up your local master branch to track the remote master branch on the server you cloned.

Pushing to Remote Branch

If you want to share your project, you have to push it upstream. The git push command is used to share a project or send updates to the remote server. It is used as:
1. $ git push <remote><branch>
To update the main branch of the project, use the below command:
1. $ git push origin master
It is a special command-line utility that specifies the remote branch and directory. When you have multiple branches on a remote server, then this command assists you to specify your main branch and repository.
Generally, the term origin stands for the remote repository, and master is considered as the main branch. So, the entire statement “git push origin master” pushed the local content on the master branch of the remote location.

Git Remove Remote

You can remove a remote connection from a repository. To remove a connection, perform the git remote command with remove or rm option. It can be done as:
Syntax:
1. $ git remote rm <destination>
Or
1. $ git remote remove <destination>
Consider the below example:
Suppose you are connected with a default remote server “origin.” To check the remote verbosely, perform the below command:
1. $ git remote -v
Output:

The above output will list the available remote server. Now, perform the remove operation as mentioned above. Consider the below output:

In the above output, I have removed remote server “origin” from my repository.

Git Remote Rename

Git allows renaming the remote server name so that you can use a short name in place of the remote server name. Below command is used to rename the remote server:
Syntax:
1. $ git remote rename <old name><new name>
Output:

In the above output, I have renamed my default server name origin to hd. Now, I can operate using this name in place of origin. Consider the below output:

In the above output, I have pulled the remote repository using the server name hd. But, when I am using the old server name, it is throwing an error with the message “‘origin’ does not appear to be a git repository.” It means Git is not identifying the old name, so all the operations will be performed by a new name.

Git Show Remote

To see additional information about a particular remote, use the git remote command along with show sub-command. It is used as:
Syntax:
1. $ git remote show <remote>
It will result in information about the remote server. It contains a list of branches related to the remote and also the endpoints attached for fetching and pushing.
Output:

The above output is listing the URLs for the remote repository as well as the tracking branch information. This information will be helpful in various cases.

Git Change Remote (Changing a Remote’s URL)

We can change the URL of a remote repository. The git remote set command is used to change the URL of the repository. It changes an existing remote repository URL.
Git Remote Set:
We can change the remote URL simply by using the git remote set command. Suppose we want to make a unique name for our project to specify it. Git allows us to do so. It is a simple process. To change the remote URL, use the below command:
1. $ git remote set-url <remote name><newURL>
The remote set-url command takes two types of arguments. The first one is <remote name >, it is your current server name for the repository. The second argument is <newURL>, it is your new URL name for the repository. The <new URL> should be in below format: https://github.com/URLChanged
Consider the below image:

In the above output, I have changed my existing repository URL as https://github.com/URLChanged from https://github.com/ImDwivedi1/GitExample2. It can be understood by my URL name that I have changed this. To check the latest URL, perform the below command:
1. $ git remote -v
So, this brings us to the end of blog. This Tecklearn ‘Working with Remote Repository’ blog helps you with commonly asked questions if you are looking out for a job in DevOps. If you wish to learn Git and GitHub and build a career in DevOps domain, then check out our interactive, Version control with Git and GitHub Training, that comes with 24*7 support to guide you throughout your learning period. Please find the link for course details:

Version Control with Git and GitHub

Version Control with Git and GitHub Training

About the Course

Tecklearn has specially designed this Git and GitHub Training Course to advance your skills for a successful career in this domain. The course will cover different components of Git and GitHub and how they are used in software development operations. The course consists of important concepts like: branching & merging, how to deal with conflicts, rebasing, merge strategies, Git workflows and so on. You will get an in-depth knowledge of these concepts and will be able to work on related demos. Upon completion of this online training, you will hold a solid understanding and hands-on experience with Git.

Why Should you take Git and GitHub Training?

• Average salary of Git and GitHub Professional is $85k – Indeed.com
• Amazon, Google, Facebook, Microsoft, Twitter, & many other MNC’s worldwide use Git across industries.
• According to Grand View Research, the DevOps market size is estimated to be worth $12.85 billion by 2025. DevOps professionals are highly paid and in-demand throughout industries including retail, eCommerce, finance, and technology.

What you will Learn in this Course?

Introduction to DevOps
• What is Software Development
• Software Development Life Cycle
• Why DevOps?
• What is DevOps?
• DevOps Lifecycle
• DevOps Tools
• Benefits of DevOps
• How DevOps is related to Agile Delivery
• DevOps Implementation
Git and GitHub
• What is version control
• Version Control System (VCS) Products
• Types of VCS
• What is Git
• Why Git for your organization
• Install Git
• Common commands in Git
• Working with Remote Repositories
• GitHub
• Git Installation
• Git Lifecycle
• GitHub (Push, Pull Request)
• GitHub Workflow

422