Pushing code to Remote Repository (GITHUB)

Learn more from the full course
REST API Automation:REST Assured,Serenity BDD Framework
Build a robust REST API test automation framework/CI environment using Serenity BDD, Jenkins, Git
05:28:09 of on-demand video • Updated July 2023
Build reusable methods ,write different types of tests
Create Data Driven Tests
Execute Tests Faster by running them in parallel
Run selective tests JUnit using Tags
Publish amazing reports with logging of Request & Response Information
Write Cucumber Scenarios integrated with Serenity BDD
Commit code to Github
Implement CI by integrating project with Jenkins & GIT
English [Auto]
This lecture, we be learning how to create a remote repository and GetUp will also learn how to push our code that is present at the local repository onto the remote repository on GitHub. This is the homepage of GitHub. So this is a you are on GitHub dot com. So what do you need to do is you need to first sign up for a guitar backup. If you already have one, then it's fine. If not, you can just create an account. And. Next year to sign into your account. I'm just going to sign it. So when you sign it for the first time, this is how the. Landing page will look so in order to create a remote repository, all you need to do is to start a new project. So in this project now, you'll have the option to create a new repository. So I named this repository as. Sorrenti. Tutorial. I just give a description. There are two settings here. One is the public setting and one is the private setting. So by default, the setting will be in public because it would be so sharing platform for collaboration as well as photo sharing. So whatever projects you're are creating on GitHub, they will be available to anyone. So if they have your GitHub, they can go and look at their project. The other option is private. So if you choose private, then you'll basically have to. Pay some amount to get help. So when you select a private GitHub account, in this case, the code won't be visible to other people. That is, repositories are now protected. Unless you give access, nobody can come and look at the code. So for our kids, we'll just be using the public setting. I did in companies, we wouldn't be actually using the GitHub dot com, rather, the servers would be hosted internally so only you can access the code within your network and not outside. This particular step and click create repository. And once we do this, we'll get some instructions on how to actually. Import the. Local repository to remote, that is how to basically push the code from our local to the GitHub repository. So these are the instructions. So let us not follow this. The first one is basically when you are doing it for the first time, that is when you create a new local repository and when you are trying to basically commit this particular local repository to the GitHub, then you basically to follow these steps. But in our case, we already created the local repository and we need to not push this to the remote. So in order to push this to the remote repository. We need to use this particular command that is get remote at origin. And this is the you are in. Let me just copy this. And here's the sort to clear this. And if I hit enter. I should have been prompted with the username and password, that is when you enter this particular command, the first time prompted by the username and password, you provide the same username and password that you used to log in to GitHub. So when you hit enter, you'll be password with that username and password. So provide those two details. And once you do that, you'll be ready to push your code to the remote repository. So before that, this recording itself, I had accidentally entered the username and password and hence it did not prompt me. So just don't be confused for the first time when it asks you for the username and password, just provide the GitHub username and password. The next step is to basically push the court to the remote repository. So in order to do that. This copy, this Bush. My initial origin, master. If I hit, enter. It will basically push all the fires that are on my local repository to the remote repository. Now, if I go back. And if I just. Open this. Repository. Now you can see that. The student project is committed to the remote repository, all the files are present here. These are all the dissociates. So this is how we basically put all the code that is present in our local repository to the remote repository on GitHub, and the first example, what we did was we created the local repository and we pushed all the code into a remote repository. How they can be cases where you are actually new to the project and you might have to get the project onto your local or basically the remote repository. So how do you do that? So in order to do that, what do you need to do is go to the project and you'll always have you are for cloning. So just copy this. You are in. And. And open up the terminal. And create a new directory. So. Right, I want to just navigate to the desktop. And Harimoto. Create another directing. This call, this austerity remote. I know, let me navigate this directly. So now I'm in the Senate report directly, so I'm going to do now is I'm basically going to close this particular project onto this Senate report directly. So all the court files will be downloaded onto this folder along with the. doGet father also will be created, there is a local repository for use, the clone Keywood. Before that. Be sure to get. Gitlow and I just need to provide you are in another fight, enter. So, you know, it's basically cloning this particular project onto this directly, and I've had to less minus and you can see here that the. Projector's. Display, so me just. Navigate here. And do unless minus in. So inside this, you can see the docket for the results of president. So we have one more for that, so if you navigate inside this folder, you have the project as well as the local repository. So with this, I think the lectures on guitar and guitar complete.