1. 26 Dec, 2017 2 commits
  2. 21 Dec, 2017 2 commits
  3. 20 Dec, 2017 8 commits
  4. 19 Dec, 2017 1 commit
  5. 18 Dec, 2017 1 commit
  6. 16 Dec, 2017 2 commits
  7. 15 Dec, 2017 3 commits
  8. 29 Nov, 2017 3 commits
    • Remy Suen's avatar
      Change function calls to field accesses instead · c45e978f
      Remy Suen authored
      In details-for-tree-entry.js, there are several calls to functions of
      an IndexEntry. However, those are actually fields on an object
      instead of prototype functions so referring to them as functions will
      cause a ReferenceError to be thrown. The fix is to not refer to them
      as functions but to simply refer to them as fields instead.
      Signed-off-by: default avatarRemy Suen <remy.suen@gmail.com>
      c45e978f
    • Remy Suen's avatar
      Add tests for AnnotatedCommit · 88d70747
      Remy Suen authored
      fromFetchhead
      fromRevspec
      88d70747
    • Remy Suen's avatar
      Add JavaScript version of `git_tag_peel()` · 19e24053
      Remy Suen authored
      The git_tag_peel() function from libgit2 naturally takes a pointer as
      a parameter for providing the caller with the peeled object. However,
      this kind of API does not make sense in the JavaScript world so we
      need to change the generated code to return the actual object to the
      caller.
      19e24053
  9. 28 Nov, 2017 5 commits
  10. 28 Oct, 2017 1 commit
    • Remy Suen's avatar
      Expose JavaScript function name in thrown error · 63f2dac2
      Remy Suen authored
      When an error happens in libgit2, NodeGit will wrap the and expose
      the error code and message to be consumed via the JavaScript API.
      However, this information is often insufficient given the
      asynchronous nature of NodeGit and it may at times be unclear as to
      which JavaScript function caused the error on the libgit2 side. By
      exposing an 'errorFunction' property string that includes the name of
      the JavaScript function in the error, debugging should now be a lot
      easier as clients will now be able to quickly identify which
      JavaScript function in a long promise chain was the source of an
      error.
      Signed-off-by: default avatarRemy Suen <remy.suen@gmail.com>
      63f2dac2
  11. 19 Oct, 2017 1 commit
  12. 18 Oct, 2017 1 commit
  13. 16 Oct, 2017 1 commit
  14. 13 Oct, 2017 4 commits
  15. 10 Oct, 2017 4 commits
  16. 28 Sep, 2017 1 commit