Fix clone options on guides

kamimoo · kamimoo · commit 5ec02f575e0e · 2016-01-11T10:43:41.000+09:00
diff --git a/guides/cloning/README.md b/guides/cloning/README.md
@@ -83,8 +83,10 @@ to passthrough the certificate check.
 *Note: this is not a problem with Windows or Linux*
 
 ``` javascript
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; }
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; }
+  }
 };
 ```
 
diff --git a/guides/cloning/gh-two-factor/README.md b/guides/cloning/gh-two-factor/README.md
@@ -99,8 +99,10 @@ to passthrough the certificate check.
 *Note: this is not a problem with Windows or Linux*
 
 ``` javascript
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; }
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; }
+  }
 };
 ```
 
@@ -112,13 +114,15 @@ callback that expects credentials to be passed.
 This function will be attached below the above `certificateCheck`, and will
 respond back with the OAuth token.
 
-The `remoteCallbacks` object now looks like this:
+The `fetchOpts` object now looks like this:
 
 ``` javascript
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; },
-  credentials: function() {
-    return NodeGit.Cred.userpassPlaintextNew(GITHUB_TOKEN, "x-oauth-basic");
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; },
+    credentials: function() {
+      return NodeGit.Cred.userpassPlaintextNew(GITHUB_TOKEN, "x-oauth-basic");
+    }
   }
 };
 ```
diff --git a/guides/cloning/gh-two-factor/index.js b/guides/cloning/gh-two-factor/index.js
@@ -20,10 +20,12 @@ var cloneOptions = {};
 
 // This is a required callback for OS X machines.  There is a known issue
 // with libgit2 being able to verify certificates from GitHub.
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; },
-  credentials: function() {
-    return NodeGit.Cred.userpassPlaintextNew(GITHUB_TOKEN, "x-oauth-basic");
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; },
+    credentials: function() {
+      return NodeGit.Cred.userpassPlaintextNew(GITHUB_TOKEN, "x-oauth-basic");
+    }
   }
 };
 
diff --git a/guides/cloning/index.js b/guides/cloning/index.js
@@ -16,8 +16,10 @@ var cloneOptions = {};
 
 // This is a required callback for OS X machines.  There is a known issue
 // with libgit2 being able to verify certificates from GitHub.
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; }
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; }
+  }
 };
 
 // Invoke the clone operation and store the returned Promise.
diff --git a/guides/cloning/ssh-with-agent/README.md b/guides/cloning/ssh-with-agent/README.md
@@ -81,8 +81,10 @@ to passthrough the certificate check.
 *Note: this is not a problem with Windows or Linux*
 
 ``` javascript
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; }
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; }
+  }
 };
 ```
 
@@ -95,13 +97,15 @@ This function will be attached below the above `certificateCheck`, and will
 respond back with the credentials from the agent.  You'll notice we handle
 the second argument passed to credentials, `userName`.
 
-The `remoteCallbacks` object now looks like this:
+The `fetchOpts` object now looks like this:
 
 ``` javascript
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; },
-  credentials: function(url, userName) {
-    return NodeGit.Cred.sshKeyFromAgent(userName);
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; },
+    credentials: function(url, userName) {
+      return NodeGit.Cred.sshKeyFromAgent(userName);
+    }
   }
 };
 ```
diff --git a/guides/cloning/ssh-with-agent/index.js b/guides/cloning/ssh-with-agent/index.js
@@ -15,14 +15,16 @@ var cloneOptions = {};
 
 // This is a required callback for OS X machines.  There is a known issue
 // with libgit2 being able to verify certificates from GitHub.
-cloneOptions.remoteCallbacks = {
-  certificateCheck: function() { return 1; },
-
-  // Credentials are passed two arguments, url and username. We forward the
-  // `userName` argument to the `sshKeyFromAgent` function to validate
-  // authentication.
-  credentials: function(url, userName) {
-    return NodeGit.Cred.sshKeyFromAgent(userName);
+cloneOptions.fetchOpts = {
+  callbacks: {
+    certificateCheck: function() { return 1; },
+
+    // Credentials are passed two arguments, url and username. We forward the
+    // `userName` argument to the `sshKeyFromAgent` function to validate
+    // authentication.
+    credentials: function(url, userName) {
+      return NodeGit.Cred.sshKeyFromAgent(userName);
+    }
   }
 };
 
