Click on 'Set Up Git' to get started. GitHub exists because of a version control application called git. The site is based around how git works, and git is pretty old. It runs via the command line and has no fancy graphical user interface. Since it's made to manage code you wrote, this shouldn't sound too scary. Of course, as previously mentioned, GitHub did make wonderful software to allow you to use their service without the command line but that won't help you too much unless you know the basics.
Git works by reading a local code repository just a folder containing code for your project on your computer and the mirroring that code elsewhere in this case, GitHub's servers. Initially we'll commit i. As you continue to work on your code, you'll simply commit changes. GitHub will then keep track of the changes you made, creating different versions of files so you can revert back to old ones if you want or just keep track of those changes for other reasons.
This is primarily why you'd want to use a version control system like git on your own, but additional benefits surface when using git to manage code with other people working on your project.
When multiple developers commit code with git, GitHub becomes a central repository where all the code that everyone's working on can stay in sync. You'll commit your changes, and other developers will pull them i. You'll do the same with their code. Git makes this all happen, so you need to download the latest version and install it. On OS X, you'll just install the command line app. On Windows, you'll get a few more items. We'll discuss how they work in the next step.
To set up git, you need to make your way into the command line. When you're ready, tell git your name like this:. You can put in any name you like, but afterwards you'll need to input your email and that email must be the email you used when signing up for GitHub:.
If, for whatever reason, you signed up for GitHub with the wrong email address, you'll need to change it. Now, to avoid always entering your login credentials and generating SSH keys, you'll want to install the credential helper so your passwords are cached.
Create an account. Edit this Article. We use cookies to make wikiHow great. By using our site, you agree to our cookie policy. Cookie Settings. Learn why people trust wikiHow. Download Article Explore this Article methods. Related Articles. Article Summary. Method 1. After navigating to the website log into your account, or create a new account.
Navigate to the repo you want to download or clone. Click the green Clone or Download button on the right. Did this summary help you?
Yes No. Log in Social login does not work in incognito and private browsers. Please log in with your username or email to continue. No account yet? Create an account. Edit this Article. We use cookies to make wikiHow great. By using our site, you agree to our cookie policy.
Cookie Settings. Learn why people trust wikiHow. A fork is simply your own copy of a repository. Forking a repository comes with a number of benefits. It gives you your own copy on your Github account that allows you to freely experiment with changes without affecting the original project. For example, you could find a bug in my Tip Calculator or want to add your own features. So, how do you fork a public repository?
You can head to www. In this example, we want to download docs directory from gitea repo. Right-click docs , you will see a Save as option with Developer's Download Helper icon.
Clicking on the option will automatically zip the folder and trigger the download process. The zipping process can take some time to finish, especially if the target folder contains a large number of files. In that case, please be patient and wait. You can safely switch over to another tab or application to do other things as long as you don't close Github tabs. Developer's Download Helper also supports downloading folders from Gitlab using the same process.
0コメント