Introduce Repository.MergeFetchedRefs

Make `Repository.MergeFetchHeads` public (with a slightly less
scary sounding name) so that a consumer may perform the mechanics
of a `Pull` in two steps.

1 files changed, 6 insertions, 2 deletions

diff --git a/LibGit2Sharp/Repository.cs b/LibGit2Sharp/Repository.cs
index b2dec10a..8e683487 100644
--- a/LibGit2Sharp/Repository.cs
+++ b/LibGit2Sharp/Repository.cs
@@ -1040,12 +1040,16 @@ namespace LibGit2Sharp
         }
 
         /// <summary>
-        /// Merge the current fetch heads into the branch pointed at by HEAD.
+        /// Merge the reference that was recently fetched. This will merge
+        /// the branch on the fetched remote that corresponded to the
+        /// current local branch when we did the fetch.  This is the
+        /// second step in performing a pull operation (after having
+        /// performed said fetch).
         /// </summary>
         /// <param name="merger">The <see cref="Signature"/> of who is performing the merge.</param>
         /// <param name="options">Specifies optional parameters controlling merge behavior; if null, the defaults are used.</param>
         /// <returns>The <see cref="MergeResult"/> of the merge.</returns>
-        internal MergeResult MergeFetchHeads(Signature merger, MergeOptions options)
+        public MergeResult MergeFetchedRefs(Signature merger, MergeOptions options)
         {
             Ensure.ArgumentNotNull(merger, "merger");