Question 1. It doesn’t matter if your project on computer B has not been pushed to Github yet. You can continue writing the project on computer A now, and then push it to Github and resolve the conflict when computer B is available. If your project on computer B has been pushed to Github, it is even simpler. Just pull the code on Github on computer A first.
Question 2. I think you haven’t figured out what the Git protocol is, because the only HTTP and SSH protocols commonly used on Github are the HTTP and SSH protocols, and there is no Git protocol. Since you have used Github, you don’t know how to push projects using the SSH protocol. Bar?
Your code on A was not pushed to the remote in time. Manually modify the conflicts. In fact, you can treat your two computers as two people and create their own branches from the server git clone master.
![[Web front-end] Node.js quick start](https://img.php.cn/upload/course/000/000/067/662b5d34ba7c0227.png)
Question 1. It doesn’t matter if your project on computer B has not been pushed to Github yet. You can continue writing the project on computer A now, and then push it to Github and resolve the conflict when computer B is available. If your project on computer B has been pushed to Github, it is even simpler. Just pull the code on Github on computer A first.
Question 2. I think you haven’t figured out what the Git protocol is, because the only HTTP and SSH protocols commonly used on Github are the HTTP and SSH protocols, and there is no Git protocol. Since you have used Github, you don’t know how to push projects using the SSH protocol. Bar?
Your code on A was not pushed to the remote in time. Manually modify the conflicts. In fact, you can treat your two computers as two people and create their own branches from the server git clone master.