Return to Answer

On the plane, you could make changes to your local workspace and then merge it with what you've previously fetched and then resolve potential merge conflicts all without a connection to the Internet. And unless someone had made new changes to the remote repository then once you arrive at the destination you would do git push origin <branch> and go get your coffee.

On the plane, you could make changes to your local workspace and then merge it with what you've previously fetched and then resolve potential merge conflicts all without a connection to the Internet. And unless someone had made new changes to the remote repository then, upon arrive at the destination you would do git push origin <branch> and go get your coffee.

1. ls. This will show the files & directories. Nothing cool, I know.

2. Now do ls -a. This will show dot files, i.e., files beginning with . You will then be able to see a directory named: .git.

3. Do cd .git. This will obviously change your directory.

4. Now comes the fun part; do ls. You will see a list of directories. We're looking for refs. Do cd refs.

5. It's interesting to see what's inside all directories, but let's focus on two of them. heads and remotes. Use cd to check inside them too.

6. Any git fetch that you do will update the pointer in the /.git/refs/remotes directory. It won't update anything in the /.git/refs/heads directory.

7. While any git pull will first do the git fetch, update items in the /.git/refs/remotes directory, will then also merge with your local and then change the head inside the /.git/refs/heads directory.

1. ls. This will show the files & directories. Nothing cool, I know.

2. Now do ls -a. This will show dot files, i.e., files beginning with . You will then be able to see a directory named: .git.

3. Do cd .git. This will obviously change your directory.

4. Now comes the fun part; do ls. You will see a list of directories. We're looking for refs. Do cd refs.

5. It's interesting to see what's inside all directories, but let's focus on two of them. heads and remotes. Use cd to check inside them too.

6. Any git fetch that you do will update the pointer in the /.git/refs/remotes directory. It won't update anything in the /.git/refs/heads directory.

7. Any git pull will first do the git fetch and update items in the /.git/refs/remotes directory. It will then also merge with your local and then change the head inside the /.git/refs/heads directory.

1. ls. This will show the files & directories. Nothing cool, I know.

2. Now do ls -a. This will show dot files, i.e., files beginning with . You will then be able to see a directory named: .git.

3. Do cd .git. This will obviously change your directory.

4. Now comes the fun part; do ls. You will see a list of directories. We're looking for refs. Do cd refs.

5. It's interesting to see what's inside all directories, but let's focus on two of them. heads and remotes. Use cd to check inside them too.

6. Any git fetch that you do will update the pointer in the /.git/refs/remotes directory. It won't update anything in the /.git/refs/heads directory.

7. Any git pull will first do the git fetch, update items in the /.git/refs/remotes directory, then merge with your local and then change the head inside the /.git/refs/heads directory.

1. ls. This will show the files & directories. Nothing cool, I know.

2. Now do ls -a. This will show dot files, i.e., files beginning with . You will then be able to see a directory named: .git.

3. Do cd .git. This will obviously change your directory.

4. Now comes the fun part; do ls. You will see a list of directories. We're looking for refs. Do cd refs.

5. It's interesting to see what's inside all directories, but let's focus on two of them. heads and remotes. Use cd to check inside them too.

6. Any git fetch that you do will update the pointer in the /.git/refs/remotes directory. It won't update anything in the /.git/refs/heads directory.

7. While any git pull will first do the git fetch, update items in the /.git/refs/remotes directory, will then also merge with your local and then change the head inside the /.git/refs/heads directory.