Using Git Support in NetBeans IDE. (Skip if using SSH-agent or Pageant for automated SSH access to the Git server.) Complete the following steps to access the Git server using your private SSH key and a passphrase. At the Update Local References page, choose the branch(es) to be updated in the Remotes directory of your local repository.

• Github-for-mac Hai Eseguito Git Update-server-info Errore Su Unit

If you are running Mac OS 10.9 (Mavericks) and later you may want to check out and install different Git version then the one noted below. In this post I’ll walk through the several steps needed to have a running GitHub account synched to a local Git.

• Join GitHub today. GitHub is home to over 28 million developers working together to host and review code, manage projects, and build software together.
• The next time you git fetch, git pull, or git push to the remote repository, you'll be asked for your GitHub username and password. If you have two-factor authentication enabled, you must create a personal access token to use instead of your GitHub password.

Github-for-mac Hai Eseguito Git Update-server-info Errore Su Unit

If all these words sounds too intimidating to you I’ll explain it briefly in the text paragraph. “ is a free and open source distributed version control system designed to handle everything from small to very large projects with speed and efficiency” – source code developers are creating is being managed by version control systems and Git is an open source (and free) example of that. “ is a web-based hosting service for software development projects that use the Git revision control system.” – essentially GitHub makes a connection between what is being managed on your computer and enable internet access to it so other people can have access to your code too. Creating GitHub Account Use your browser to create a free account at ‘s website.

It’s pretty straightforward. After you are done with that follow guide to create your first repository on GitHub. Installing Git on Your Mac (no XCode is needed) Now it’s time to move to your computer and install Git. While writing these lines the latest Git version for Mac wasn’t compatible with Mac OS 10.8 so I needed to look elsewhere. I found a.dmg Git versions and downloaded the latest version that supported Mac 10.8 – 2.0.5 from following the guidelines that are found in this downloading website (in my case taking the latest snow-leopard version). 10.6 Snow Leopard: git-.-snow-leopard. 10.7 Lion: git-.-snow-leopard.

10.8 Mountain Lion: git-.-snow-leopard. 10.9 Mavericks: git-.-mavericks. 10.10 Yosemite: git-.-mavericks After clicking the.dmg file open your Mac Terminal window.

This is well described in this very short video. Getting Things Ready Now that you have your Git installed properly and you have set your Github account and created one repository in it we can get to business. But before we do that, we’ll follow some basic required steps. First things first, let’s verify things are installed correctly by checking our Git version terminal window. $ git -version git version 2.0.5 Tell Git your name so your commits will be properly labeled. $ git config -global user.name ' YOUR NAME' Tell Git the email address that will be associated with your Git commits. The email you specify should be the same one found in your GitHub email settings.

To keep your email address hidden, see ““. $ git config -global user.email ' YOUR EMAIL ADDRESS' There are two ways to authenticate from GitHub to Git – SSH. I’ll use the latter so let’s save some time using our GitHub user and password later on by using the credential-oskeychain command. $ git credential-osxkeychain usage: git credential-osxkeychain And finish up by typing the following: $ git config -global credential.helper osxkeychain The next time you clone an HTTPS URL that requires a password, you’ll be prompted for your username and password, and to grant access to the OSX keychain.

After you’ve done this, the username and password are stored in your keychain and you won’t be required to type them in to Git again. Basic Work with Repository Finally! We are ready to start working with our repository.

We first want to use the clone command to have our GitHub repository cloned to our computer. You’ll find the URL for your repository by following this guide $ git clone Cloning into 'OpenStackFiles'. Remote: Counting objects: 9, done. Remote: Compressing objects: 100% (6/6), done. Remote: Total 9 (delta 0), reused 0 (delta 0), pack-reused 0 Unpacking objects: 100% (9/9), done. Checking connectivity.

We’ll change directory on our computer so then we can use the status command to check the differences between our local repository and the remote GitHub repository yaniv-zadkas-macbook:OpenStackFiles yanzadka$ git status On branch master Your branch is up-to-date with 'origin/master'. Nothing to commit, working directory clean We can use the pull command to fetch whatever been updated on our GitHub repository to our computer local one.

Yaniv-zadkas-macbook:OpenStackFiles yanzadka$ git pull Next we can use the add command to a “stage” for commit after creating a file called test.txt yaniv-zadkas-macbook:OpenStackFiles yanzadka$ git add test.txt add has few more options. You can read about it. Now that our file is past it’s “staging” process we can commit it to our local repository yaniv-zadkas-macbook:OpenStackFiles yanzadka$ git commit -m test.txt 'committing test.txt file' And last, in order to have it available on our GitHub repository we’ll use the push command yaniv-zadkas-macbook:OpenStackFiles yanzadka$ git push test.txt We can now refresh our GitHub OpenStackFiles repository and find out that the file test.txt is available there.

I would highly recommend the first 14 minutes of video to have a better understanding of Git and GitHub basic functionality.

There are a few common errors when using HTTPS with Git. These errors usually indicate you have an old version of Git, or you don't have access to the repository.

Here's an example of an HTTPS error you might receive: error: The requested URL returned error: 401 while accessing user/ repo.git/info/refs?service=git-receive-pack fatal: HTTP request failed Error: The requested URL returned error: 403 while accessing user/ repo.git/info/refs fatal: HTTP request failed Error: user/ repo.git/info/refs not found: did you run git update-server-info on the server? Check your Git version There's no minimum Git version necessary to interact with GitHub, but we've found version 1.7.10 to be a comfortable stable version that's available on many platforms. You can always. Ensure the remote is correct The repository you're trying to fetch must exist on GitHub, and the URL is case-sensitive. You can find the URL of the local repository by opening the command line and typing git remote -v: git remote -v # View existing remotes origin (fetch) origin (push) git remote set-url origin # Change the 'origin' remote's URL git remote -v # Verify new remote URL origin (fetch) origin (push) Alternatively, you can change the URL through our application. Provide an access token If you have enabled, or if you are accessing an organization that uses, you must instead of entering your password for HTTPS Git.

Check your permissions When prompted for a username and password, make sure you use an account that has access to the repository.