Permalink
Checking mergeability…
Don’t worry, you can still create the pull request.
Comparing changes
Choose two branches to see what’s changed or to start a new pull request.
If you need to, you can also or
learn more about diff comparisons.
Open a pull request
Create a new pull request by comparing changes across two branches. If you need to, you can also .
Learn more about diff comparisons here.
...
- 18 commits
- 96 files changed
- 8 contributors
Commits on Apr 12, 2018
-
Expose error codes to fix unused variable warnings
Signed-off-by: Remy Suen <remy.suen@gmail.com>
Commits on Aug 12, 2018
Commits on Aug 29, 2018
-
Merge pull request nodegit#1534 from dwelle/patch-1
warn about node v10 incompatibility in readme
Commits on Aug 31, 2018
-
Merge pull request nodegit#1486 from rcjsuen/unused
Define error codes to fix compiler warnings about unused variables
Commits on Sep 19, 2018
-
-
The `test` function is required to force promisify-node to promisify native functions, because async inference based on argument's names cannot work on native functions. With promisify-node ~0.3.0, functions were always promisify, even if they were not considered asynchronous by async inference.
-
Fixed cannot read property 'name' of null error
In `promisify-node~0.3.0`, function `processExports` in `index.js` don't add `null` checking for `exports` argument.It got fixed in `promisify-node~0.5.0`.
-
-
-
-
-
-
-
-
-
See nodegit#1490 (comment) Co-Authored-By: Mehdi Yeganeh <myeganeh1984@gmail.com>
-
Revert "warn about node v10 incompatibility in readme"
This reverts commit b76fd67.
Loading
This comparison is taking too long to generate.
Unfortunately it looks like we can’t render this comparison for you right now. It might be too big, or there might be something weird with your repository.
You can try running this command locally to see the comparison on your machine:
git diff master...master