#1 APA ITU GIT & GITHUB?

Hello friends, how are you? Hopefully you are all healthy. Welcome back to the Unpassed web programming channel with me, Sandika Gali. And this time we will start a new series. This series is quite important for you programmers or programmers. So in this series we will discuss what is Git and what is GitHub.

And why are they important to us programmers? And I know this topic is not an easy topic So I will try as much as possible so that the material is not too difficult So if at the end of this video you are still confused with the explanation Don't worry, because in this video we will only discuss the concept, definition, and theory Only start the next video, then we will practice

to use GitHub and Git but one thing you have to pay attention to and have to remember from the beginning this is Git and GitHub, friends, are two different things so you can just work with Git without GitHub or vice versa, you can use GitHub but your computer doesn't install Git

So it can really be separated, but we can also combine it. Well, that's it at the beginning, so you don't get confused. Because when I first learned, I was also confused whether GitHub and Git are something that we must use together or not. And the answer is no, they can be separated. We'll see one by one later. First of all, let's discuss Git. What is Git?

So, in a simple way, Git is one of the things that called VCS or Version Control System So, we have to discuss first, what is Version Control System? If you guys check the definition on Wikipedia

You can see this, please read it, it says version control system or we can also call it revision control system or someone says source code management or SCM So it is a system that manages the changes in a document, it can be a file, it can be a source code or a website or any information that you make digitally on a computer

You can see the detailed explanation on Wikipedia The point is a system that can manage changes in our documents

Now why do we have to use VCS or version control system? There are several problems or problems that often arise Maybe you have or often even experienced this The first one, I have an example of this case I often do this for my students So the story is, for example, a student wants to work on a script or final task Maybe at the beginning of the script, they make a file called "my script" for example

Well, later, as time goes by, the student's guidance to the tutor's teacher, the script is revised. Well, imagine, friends, if it's already revised, the script report will definitely change. Later, the report will increase. So, there is a revision 1. If there is another revision,

Add the revision again, revision 2, revision 3, even if it's getting more and more reports are getting more and more And even at the end, maybe I often see when they are in court I asked to show the report, the file name is already various, like this

This is our manual way to manage the version of our file We often do this, whether it's a document or a source code, maybe you store it in different folders with different file names This is the manual version of the control, it has not been managed using VCS So using VCS this doesn't happen again because the management is done quite well using VCS

So the first problem is that we have a hard time making a version for our file Now there is the next problem, this is specific if earlier it could be in a document that is not software, not source code If this is for example you want to make software, want to make a program, want to make an application

The story is that you are coding, you are coding yourself, for example, making a website, you are working on the display, working on the backend, the database itself, it's actually no problem, right? You can store it in your computer, whether it's a task, or a project, or a job. Well, it will be quite troublesome when you work as a team.

For example, two people or three people. For example, you guys at school or at campus, you get the task of making software.

create a website, maybe you will share the work, one person works on the display or front-end, one person works on the backend or one person works on the database, for example, or everyone works on the same web but the features are different, what do you do, what do you do, what do you do, that's it, so it means like this, friends, there must be different source codes on each computer,

It will be quite troublesome when it has to be combined into one. It will definitely be collected or if you want to be the application, you have to be combined first. Is it true? Well, this collaboration process, working together, is called a collaboration process. Well, if without VCS or version control system, it's quite troublesome because it has to be manual. And this is also a problem that can be handled by version control. So, there are two main things. Why do we use

using version control, we can track the version or history of the change that happens on our software. The second is when collaborating. Well, actually there will be another third when you want to share, share or display the product that you have made to others. But we'll see that later. But up to here I understand, what is the use of VCS?

Now maybe you guys are thinking, "What's the difference between applications like Dropbox or Google Drive or Google Docs?" It can actually do the same thing, it can solve the problem of the second one. You can store history, in Google Docs it can also work collaboratively. You work on one Excel file using Google Docs, but both. Which one edits which line, which one edits which line, for example.

Well, it's true, these two software can solve the two problems we discussed earlier. But not as flexible as when we use the version control specifically for source code. Because these two applications are designed to work on files that are not source code.

So using this is not accurate if we want to manage source code with these two. Understand, friends? Okay, now let's look at the definition of the version control system. We conclude that this version control system is a system that can store a recam, which we will later call a recam or snapshot of the changes that occur in our source code.

So we don't need to make a manual version, copy paste, change the name, no need The second, by using the version control, we can work collaboratively better Because later the version controller knows who changes what, when it changes Which one is missing the line, which one is added So we can know who makes the change and when

The change happens And the last one, allows us to return to the situation before we make a change So if you have made some changes, it turns out

the change is not accurate or you feel it doesn't fit with the changes that are made. Wow, this feature doesn't seem good. I want to go back again before there is this feature, with the control version it can be done. By using a technique called Checkout. So that's about the version control system. And I said Git is one of the version control systems.

Actually, besides Git, there are many others. You can see that besides Git, there is a subversion or SVN. If you search, you will find SVN. It is also the version of the Control System. There is another one called Mercurial. And there is another one called CVS. Or if I'm not mistaken, it's called Concurrent Version System.

So what we will use in this series is Git. So that's the short explanation about the Control System version. Now we go to Git itself. So what is Git? Let's see. If you check on Wikipedia, it says this: Git is a distributed Control System version that can be used to manage files in folders. The short explanation is that.

And if you see the Wikipedia, please read it, the story is interesting, this is made by a Linux maker The reason why he made it and why the name Git is interesting to read So friends, please visit the Wikipedia if you want to know But the point is, Git is VCS that allows us to manage files in the folder

or in short, it's just software, software that you will install on your computer so that it can easily manage files in the folder and later the file in the folder or the folder, the folder will be called a repository or repo so if for example now you have made a folder in htdocs, for example, we make it together, follow the basic php series, follow

OOP, HP, MVC, or Codeigniter You must have made a new folder in htdocs Later, when you talk about Git, it's not called a folder anymore But it's called a repository

or repo or repo, understand? and later git is, you understand the term first, before repo already, then next like this git will store every change sequence or change history, here friends can see by using something called commit

You also have to know the term, we will use it very often So if we make a change, it's usually just save, Ctrl + S, done Well, if you have worked with Git, not only Ctrl + S that you do later But you have to commit a commit Well, what was the save just now? Which part? Can you add what feature? Erase which line? That's called commit And later after you commit

The git will record the snapshot So one commit will be recorded by one snapshot Understand? Next, for example If you make changes without git Without version control system We already know that you can see a lot of files With different names, although maybe the content is just a little bit more Add one bump, add one page Delete several rows But the file becomes a lot

This is if without Git, and later if we do this with Git, what happens is the file becomes only one, the file becomes only one Later Git is smart enough to store the history of the change, which we mentioned earlier with commit

If you see the blue dots, we consider it as a commit. That means we have committed 5 times. For example, the first thing you do is start working on the first page. For example, this is still a script, for example. Later, the first page is finished, saved, and committed once. Give the message, "I'm starting to work on the first page." Next, you work again. For example, the next one is adding the background. That's the next commit. Later, Git will edit that. Commit again, for example.

commit again and so on, what is being recoded by git is the history of changes in the form of commit if we put it in source code, for example you want to make a program, not a script document again you can assume this, for example we make if you follow the login series using Codingnator for example in the htdocs there must be a wpu login folder for example

Well, later, if this WPU login is to be used using Git, we will initialize first that this is not a folder now, but a repo or repo, a repository. Well, if we have already told that the folder is now a repository, then Git will monitor every change that happens. If we don't do that, it's just a normal file. Well, after the Git monitors it,

it will only store every change we make. For example, the first time you initialize the project, it's still empty, only the codigniter is empty. Then next, you add a view to login. Add this, you've coded, using VS Code for example, or using Sublime Text, it's done, saved, not finished yet. You commit first, tell the Git, I've made this change.

Later saved with the git Understand ya, and so on until the project is finished, for example So, if at some point you want, "Wow, this seems to have a feature that doesn't fit" You just go back Check out which commit, like that Understand ya

Well, if you want to know what is in the commit, what is the Git stored in each commit? Besides, it's the change, okay? Now if we look at it, if we look at one of the commits, for example, the one that makes this controller user, the content is like this.

So inside, you see, the first row you see there is a commit, then next to it there is a long number, then the number is not clear, right? Well, this is called hash, the marker for each commit So every time we commit, we make a hash or a very long random string

So that the Git can track this OHash for this commit Then below there is another one, who committed it This is really useful when you are working on the project team Later you will know who edits this, who erases this Then there is also when to commit it And the last one is quite important is the message of the commit, the commit message

So every commit you have to let them know what you did just now So don't just save it That's it, friends, so with Git now it's more organized Now next, when you make a repo and you have committed it later Visually, you saw the point below the commit, right? Well, actually later it will be easier if we see it horizontally Okay, if you see it like this, it means there is a repo that has been committed three times Understand ya

Now, the story is after I worked on three commits, I thought, "Oh, this is like when I commit the second, I will make a new feature." But I'm not sure about the feature. Well, that means from the second commit, I can do it like a branch, so as not to disturb the main commit path. Well, here I made a commit A, made a copy, or this case can only be if the team works.

I work on the commit in the middle, your friends work on other features. At first it's the same, using the initial project. But divided, you do this, you do this, in the same repo. It can be like that. Well, this we call a branch. The term is "digit", or branch.

Well, later, for example, the story of the branch or the new feature earlier, it has been done several times, the commit turns out that the feature wants to be used, then it means that later we want to plant the feature in the main commit or you want to combine the work of two people, later this can be combined, yes, the process of combining this, combining two branches is called Merge, yes, this is also an expression of Git.

So I've given you some of the gate terms that you need to understand. Understand? Until here. Now, all we did earlier, making commits, making branches, then merging, you can do it in

your own computer, so it's local, so you do it yourself, as long as the requirement is that your computer must install Git software, that's why I said at the beginning we can separate between Git and GitHub because you can install Git then you manage your own software, there is no connection with others, using Git locally, hopefully you guys understand

Next, we will discuss about GitHub. What is GitHub? It's simple. GitHub is a website that you can visit, register as usual. The website is here, github.com. You create an account.

Then you can upload files or create files there Later the file can be managed using the control version It has GitHub So you don't need to install Git on your computer This is the opposite, you can work on GitHub

without installing Git. So the short definition is GitHub is a cloud service. Not just a regular website, but it is a cloud service to store and manage projects or Git repositories. Or in my term, this is Instagram for programmers. So if Instagram is a place for you to store photos, show good photos, others can like, and so on. Git is the same, but what you upload is a project.

or repo or source code so that others can see, like, even modify what you do and so on. Although I know that some of you will think the term is not accurate, but it's that easy. The point is that this GitHub can do the same thing as what we did earlier in the local, in our computer. So in GitHub, you can also make a repo, commit, make a branch, merge,

Same, the difference is only this is done online, in the cloud, through the internet So you go to the website, make a file there, edit there, commit there Or the term GitHub is a website that uses Git inside So it's separated from the Git on your computer But the cool thing is this, what if you use GitHub online but on your computer

you also install Git, here it feels really useful when we combine the two, so here we can send our source code or our project to GitHub or vice versa, we can also take the source code or project or repo that is in GitHub to our computer, so the sending process is usually called push and the receiving process

Or taking it, we call it pull But what is pushed and pulled? What is pushed and pulled is the commit

So we take the commit or send the commit, understand? But all of this you can do, there is a condition that you can't just send it, just take it, you can't do that The condition is, first you have to make this GitHub into something called a remote, a source from your repo So you make a repo on GitHub, there will be a repo on GitHub

Your computer is already in Instagit, later the repo will be cloned We take it, clone it, so that it is also available on our computer So it connects between the repo on GitHub and the repo on your computer If this has been done, then we can push and pull the commit

So work on the computer, save, commit, done, push, send Or one day you're not on your laptop, using your friend's laptop, there's definitely no project Let's take it first, let's pull it first, then we work, we edit, it's done, save, commit, push So that's the workflow using Git So it's useful if you use both, even though you can do it yourself

Next, with the previous analogy, it will be very useful when we collaborate So now imagine, the repo is one, it's on GitHub, which many people work on, it's no problem Just connect to the same repo, he knows who can do what, who has edited what, like that

And we can also share easily, for example you have a small snippet or project that is useful, just save it on GitHub, later others can see, can modify, can like, and so on. That's it, friends, hopefully now you understand, at least the concept first. Yes, the practice is not yet, it's okay, at least the concept has been understood that Git and GitHub will be useful for us when managing our software or application or website.

Well, you must know that besides GitHub there are other services Yes, for example, you know there is a bitbucket or Gitlab Yes, these two examples can do the same thing with GitHub Yes, friends, how is it? Are you confused with the explanation? Hopefully you understand, and before we end, let's try to recap first, let's remember again What have we learned in this video? Let's try the first one, friends, we have learned about the version control system, try what it means

Version Control System is a system that makes it easier for us to store and manage changes or snapshots on our source code. Yes, that's as simple as that. Next, Git. Try Git what?

Git is one of the software that can do VCS, that's easy And the last one, GitHub If GitHub is okay, GitHub is the website, the cloud service for us to manage our Git project So with this definition, hopefully you can understand about Git and GitHub

And later on, there are several terms that you have to understand first, at least what it means, yes, these are terms or comments or commands in Git Maybe I will tell you a few, and we have already discussed some of these earlier, yes There are still several other commands that we will learn while we follow this series But try to remember again, the first one, what is repo?

Repo or repository or repo is our project folder, it's that simple Folder that we will initialize as repo git Earlier we can change the folder to repo git The second is commit What is commit?

Commit is a recommendation or snapshot of our repo in a certain situation So if you have saved, you have made a change, then you commit, that's the snapshot Then hash, what was it? A unique marker on a commit So the git can check which commit is through hash, the random number string earlier Then there is check out, what is check out?

Checkout is when we want to move to a commit For example, go back to which commit, that's called a checkout Then there is a branch What is a branch? Branch is a branch of a commit So it's a free branch, right? You can make it yourself or someone else can make it There is a merge This is the link between the branch Merge is when we combine two or more branches Then there is another remote or remote, what is it?

So remote is simply a source that has a repo You can make GitHub as a remote Or GitLab or Bitbucket as a remote So you can clone, take a repo from the remote So that it connects your repo on your computer, local, with the repo on the remote So next we can push, send a commit and pull

Take the commit from repo Okay, so maybe that's it For the preview video or the guide from Git and GitHub I hope you guys have started to have an idea If you haven't used Git and GitHub before Hopefully get an idea About how important Git and GitHub are

For those who can't wait to try Git and GitHub, in the next video we will go to GitHub first. So we will start learning GitHub first, not learning from Git first. Because I think if you learn from Git first, it's enough to confuse and intimidate.

we work with command prompt or CMD like that, so we will type it on the console, then the display is black like that, so we should first learn from the web from GitHub so that we can click, then later after you understand the usage of the terms we discussed earlier, we will move to using git on our computer using the console, so my advice before following the next video

Please try to create an account on GitHub

for those who don't have it, try to create an account, try to play with the interface of the GitHub, just try it later in the next video we will enter using GitHub, so that's it maybe for this video, thank you friends for watching, hopefully you are excited to follow the series, because once again this series is quite important for us to learn, we will meet again in the next episode, I am Sandika Ghali, goodbye and as usual friends, don't forget the comma