How to setup your own git repository

Your fork is referenced through your personal GitHub user account, such as github. Your credentials will be saved and used to authenticate future GitHub requests. You only need to do this authentication once per computer. The clone command runs and downloads a copy of the repository files from your fork into a new folder on the local disk. A new folder is made within the current folder.

It may take a few minutes, depending on the repository size. You can explore the folder to see the structure once it is finished. After cloning the repository, set up a read-only remote connection to the main repository named upstream. You use the upstream URL to keep your local repository in sync with the latest changes made by others. The git remote command is used to set the configuration value.

You use the fetch command to refresh the branch info from the upstream repository. If you're using Git Credential Manager , use the following commands. View the configured values and confirm the URLs are correct. Ensure the origin URLs point to your personal fork. Example remote output is shown. A fictitious git account named MyGitAccount is configured with a personal access token to access the repo azure-docs:. If you made a mistake, you can remove the remote value.

To remove the upstream value, run the command git remote remove upstream. Skip to main content. This browser is no longer supported. Download Microsoft Edge More info. Contents Exit focus mode. Is this page helpful? Necessary cookies are absolutely essential for the website to function properly. This category only includes cookies that ensures basic functionalities and security features of the website.

These cookies do not store any personal information. Any cookies that may not be particularly necessary for the website to function and is used specifically to collect user personal data via analytics, ads, other embedded contents are termed as non-necessary cookies.

It is mandatory to procure user consent prior to running these cookies on your website. Blog Topic. We use cookies on our website to give you the most relevant experience by remembering your preferences and repeat visits.

Close Privacy Overview This website uses cookies to improve your experience while you navigate through the website. Out of these cookies, the cookies that are categorized as necessary are stored on your browser as they are essential for the working of basic functionalities of the website.

We also use third-party cookies that help us analyze and understand how you use this website. These cookies will be stored in your browser only with your consent. You also have the option to opt-out of these cookies. But opting out of some of these cookies may have an effect on your browsing experience. Select Internet site, and then enter either the domain or the IP address of the server. If you're users are familiar with Linux, you could always select a local-only Postfix configuration, knowing that all users would have to use the mail command on the server to check to see if they have any mail delivered by GitLab.

If you do go that route, you'll need to install the mailutils package, like so:. With the dependencies ready, we must install the necessary repository with the following commands:. There is only one file to edit for configuration. Within that file, you're looking for the following line:. Modify that to reflect either your server domain or IP address. If you're using an IP address, make sure to drop the https in favor of http.

To do that, locate the following two lines around line :. Uncomment those lines remove the and then change false to true and enter a valid email address inside the empty [ ] characters. You will be prompted to change the administrator account password Figure A. Once you've done that, you'll be presented with the login screen, where you can register for an account. Create an account, log in, and you are ready to start using GitLab.

Create groups, projects, and more. In order to push or pull to your projects, you must add remote machine account ssh-keys to your new GitLab account. Back on your GitLab account, click the Profile drop-down in the upper right corner and click Settings. With the public key added, you should now be able to push and pull changes to the GitLab server.