{"push_id":2683197291,"size":34,"distinct_size":1,"ref":"refs/heads/jk/curl-auth-callback-wip","head":"1aeb1b11a1fed2a2b3c712e9bcc857808401a13f","before":"9db84dd25c60181269e55634e18334ca38240697","commits":[{"sha":"2b1c01d22ef280ef3a6efd70db2b9aa58359ee36","author":{"name":"Nguyễn Thái Ngọc Duy","email":"024f400cd820cb2ddbe54c7fecfd01e45f30bb96@gmail.com"},"message":"parse-options: option to let --git-completion-helper show negative form\n\nWhen 7fb6aefd2a (Merge branch 'nd/parseopt-completion' - 2018-03-14)\nis merged, the completion for negative form is left out because the\nseries is alread long and it could be done in a follow up series. This\nis it.\n\n--git-completion-helper now provides --no-xxx so that git-completion.bash\ncan drop the extra custom --no-xxx in the script. It adds a lot more\n--no-xxx than what's current provided by the git-completion.bash\nscript. We'll trim that down later.\n\nSigned-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/2b1c01d22ef280ef3a6efd70db2b9aa58359ee36"},{"sha":"3fe735e723102b631a5509dc5f2ce835616d92e7","author":{"name":"Nguyễn Thái Ngọc Duy","email":"024f400cd820cb2ddbe54c7fecfd01e45f30bb96@gmail.com"},"message":"completion: suppress some -no- options\n\nMost --no- options do have some use, even if rarely to negate some\noption that's specified in an alias.\n\nThese options --no-ours and --no-theirs however have no clear\nsemantics. If I specify \"--ours --no-theirs\", the second will reset\nwriteout stage and is equivalent of \"--no-ours --no-theirs\" which is\nnot that easy to see. Drop them. You can either switch from --ours to\n--theirs and back but you can never negate them.\n\nSigned-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/3fe735e723102b631a5509dc5f2ce835616d92e7"},{"sha":"f4d35a6b49621348c73222e7017a434551799308","author":{"name":"Phillip Wood","email":"2ab49fd2594d8067d004e5d20374688a2b5dc79c@dunelm.org.uk"},"message":"add -p: fix counting empty context lines in edited patches\n\nrecount_edited_hunk() introduced in commit 2b8ea7f3c7 (\"add -p:\ncalculate offset delta for edited patches\", 2018-03-05) required all\ncontext lines to start with a space, empty lines are not counted. This\nwas intended to avoid any recounting problems if the user had\nintroduced empty lines at the end when editing the patch. However this\nintroduced a regression into 'git add -p' as it seems it is common for\neditors to strip the trailing whitespace from empty context lines when\npatches are edited thereby introducing empty lines that should be\ncounted. 'git apply' knows how to deal with such empty lines and POSIX\nstates that whether or not there is an space on an empty context line\nis implementation defined [1].\n\nFix the regression by counting lines that consist solely of a newline\nas well as lines starting with a space as context lines and add a test\nto prevent future regressions.\n\n[1] http://pubs.opengroup.org/onlinepubs/9699919799/utilities/diff.html\n\nReported-by: Mahmoud Al-Qudsi <mqudsi@neosmart.net>\nReported-by: Oliver Joseph Ash <oliverjash@gmail.com>\nReported-by: Jeff Felchner <jfelchner1@gmail.com>\nSigned-off-by: Phillip Wood <phillip.wood@dunelm.org.uk>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/f4d35a6b49621348c73222e7017a434551799308"},{"sha":"dc0642218306190a2d284f47f75d71aeeaa34d02","author":{"name":"Ævar Arnfjörð Bjarmason","email":"0135fcc047f75af264c800977a73e353c6ba842d@gmail.com"},"message":"refspec: s/refspec_item_init/&_or_die/g\n\nRename the refspec_item_init() function introduced in\n6d4c057859 (\"refspec: introduce struct refspec\", 2018-05-16) to\nrefspec_item_init_or_die().\n\nThis follows the convention of other *_or_die() functions, and is done\nin preparation for making it a wrapper for a non-fatal variant.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/dc0642218306190a2d284f47f75d71aeeaa34d02"},{"sha":"c495fd3d1b4b6b395346a8832edbea25f0d60ee7","author":{"name":"Ævar Arnfjörð Bjarmason","email":"0135fcc047f75af264c800977a73e353c6ba842d@gmail.com"},"message":"refspec: add back a refspec_item_init() function\n\nRe-add the non-fatal version of refspec_item_init_or_die() renamed\naway in an earlier change to get a more minimal diff. This should be\nused by callers that have their own error handling.\n\nThis new function could be marked \"static\" since nothing outside of\nrefspec.c uses it, but expecting future use of it, let's make it\navailable to other users.\n\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/c495fd3d1b4b6b395346a8832edbea25f0d60ee7"},{"sha":"7865d157a5e8d86f46e626d933bda5c18eab196a","author":{"name":"Martin Ågren","email":"8ca556a9738b0ffc61ac245e7c4fa168b50ae1dc@gmail.com"},"message":"refspec: initalize `refspec_item` in `valid_fetch_refspec()`\n\nWe allocate a `struct refspec_item` on the stack without initializing\nit. In particular, its `dst` and `src` members will contain some random\ndata from the stack. When we later call `refspec_item_clear()`, it will\ncall `free()` on those pointers. So if the call to `parse_refspec()` did\nnot assign to them, we will be freeing some random \"pointers\". This is\nundefined behavior.\n\nTo the best of my understanding, this cannot currently be triggered by\nuser-provided data. And for what it's worth, the test-suite does not\ntrigger this with SANITIZE=address. It can be provoked by calling\n`valid_fetch_refspec(\":*\")`.\n\nZero the struct, as is done in other users of `struct refspec_item` by\nusing the refspec_item_init() initialization function.\n\nSigned-off-by: Martin Ågren <martin.agren@gmail.com>\nSigned-off-by: Ævar Arnfjörð Bjarmason <avarab@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/7865d157a5e8d86f46e626d933bda5c18eab196a"},{"sha":"9dd39821e3d0adf3f160642589291965c73a529e","author":{"name":"SZEDER Gábor","email":"d1c15c709aaa0744057ac20f93d60e563c0b84d1@gmail.com"},"message":"t7510-signed-commit: use 'test_must_fail'\n\nThe two tests 'detect fudged signature' and 'detect fudged signature\nwith NUL' in 't7510-signed-commit.sh' check that 'git verify-commit'\nerrors out when encountering a forged commit, but they do so by\nrunning\n\n  ! git verify-commit ...\n\nUse 'test_must_fail' instead, because that would catch potential\nunexpected errors like a segfault as well.\n\nSigned-off-by: SZEDER Gábor <szeder.dev@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/9dd39821e3d0adf3f160642589291965c73a529e"},{"sha":"2f3cbcd8c5a00dc043aabc13f2af221c7c0e89ad","author":{"name":"SZEDER Gábor","email":"d1c15c709aaa0744057ac20f93d60e563c0b84d1@gmail.com"},"message":"tests: make forging GPG signed commits and tags more robust\n\nA couple of test scripts create forged GPG signed commits or tags to\ncheck that such forgery can't fool various git commands' signature\nverification.  All but one of those test scripts are prone to\noccasional failures because the forgery creates a bogus GPG signature,\nand git commands error out with an unexpected error message, e.g.\n\"Commit deadbeef does not have a GPG signature\" instead of \"...  has a\nbad GPG signature\".\n\n't5573-pull-verify-signatures.sh', 't7510-signed-commit.sh' and\n't7612-merge-verify-signatures.sh' create forged signed commits like\nthis:\n\n  git commit -S -m \"bad on side\" &&\n  git cat-file commit side-bad >raw &&\n  sed -e \"s/bad/forged bad/\" raw >forged &&\n  git hash-object -w -t commit forged >forged.commit\n\nOn rare occasions the given pattern occurs not only in the commit\nmessage but in the GPG signature as well, and after it's replaced in\nthe signature the resulting signature becomes invalid, GPG will report\nCRC error and that it couldn't find any signature, which will then\nultimately cause the test failure.\n\nSince in all three cases the pattern to be replaced during the forgery\nis the first word of the commit message's subject line, and since the\nGPG signature in the commit object is indented by a space, let's just\nanchor those patterns to the beginning of the line to prevent this\nissue.\n\nThe test script 't7030-verify-tag.sh' creates a forged signed tag\nobject in a similar way by replacing the pattern \"seventh\", but the\nGPG signature in tag objects is not indented by a space, so the above\nsolution is not applicable in this case.  However, in the tag object\nin question the pattern \"seventh\" occurs not only in the tag message\nbut in the 'tag' header as well.  To create a forged tag object it's\nsufficient to replace only one of the two occurences, so modify the\nsed script to limit the pattern to the 'tag' header (i.e. a line\nbeginning with \"tag \", which, because of the space character, can\nnever occur in the base64-encoded GPG signature).\n\nNote that the forgery in 't7004-tag.sh' is not affected by this issue:\nwhile 't7004' does create a forged signed tag kind of the same way,\nit replaces \"signed-tag\" in the tag object, which, because of the '-'\ncharacter, can never occur in the base64-encoded GPG signarute.\n\nSigned-off-by: SZEDER Gábor <szeder.dev@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/2f3cbcd8c5a00dc043aabc13f2af221c7c0e89ad"},{"sha":"6cb09125bea69d9bdb461b8ecacd5c50c9e6a4f5","author":{"name":"Anthony Sottile","email":"3cda128df7a007b1c57a23ef03d8c048d589c229@umich.edu"},"message":"config.c: fix regression for core.safecrlf false\n\nA regression introduced in 8462ff43 (\"convert_to_git():\nsafe_crlf/checksafe becomes int conv_flags\", 2018-01-13) back in Git\n2.17 cycle caused autocrlf rewrites to produce a warning message\ndespite setting safecrlf=false.\n\nSigned-off-by: Anthony Sottile <asottile@umich.edu>\nAcked-By: Torsten Bögershausen <tboegi@web.de>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/6cb09125bea69d9bdb461b8ecacd5c50c9e6a4f5"},{"sha":"b221b5ab9b92f3def37184db6e052ec87d7635b4","author":{"name":"Nguyễn Thái Ngọc Duy","email":"024f400cd820cb2ddbe54c7fecfd01e45f30bb96@gmail.com"},"message":"completion: collapse extra --no-.. options\n\nThe commands that make use of --git-completion-helper feature could\nnow produce a lot of --no-xxx options that a command can take. This in\nmany case could nearly double the amount of completable options, using\nmore screen estate and also harder to search for the wanted option.\n\nThis patch attempts to mitigate that by collapsing extra --no-\noptions, the ones that are added by --git-completion-helper and not in\noriginal struct option arrays. The \"--no-...\" option will be displayed\nin this case to hint about more options, e.g.\n\n    > ~/w/git $ git clone --\n    --bare                 --origin=\n    --branch=              --progress\n    --checkout             --quiet\n    --config=              --recurse-submodules\n    --depth=               --reference=\n    --dissociate           --reference-if-able=\n    --filter=              --separate-git-dir=\n    --hardlinks            --shallow-exclude=\n    --ipv4                 --shallow-since=\n    --ipv6                 --shallow-submodules\n    --jobs=                --shared\n    --local                --single-branch\n    --mirror               --tags\n    --no-...               --template=\n    --no-checkout          --upload-pack=\n    --no-hardlinks         --verbose\n    --no-tags\n\nand when you complete it with --no-<tab>, all negative options will be\npresented:\n\n    > ~/w/git $ git clone --no-\n    --no-bare                 --no-quiet\n    --no-branch               --no-recurse-submodules\n    --no-checkout             --no-reference\n    --no-config               --no-reference-if-able\n    --no-depth                --no-separate-git-dir\n    --no-dissociate           --no-shallow-exclude\n    --no-filter               --no-shallow-since\n    --no-hardlinks            --no-shallow-submodules\n    --no-ipv4                 --no-shared\n    --no-ipv6                 --no-single-branch\n    --no-jobs                 --no-tags\n    --no-local                --no-template\n    --no-mirror               --no-upload-pack\n    --no-origin               --no-verbose\n    --no-progress\n\nCorner case: to make sure that people will never accidentally complete\nthe fake option \"--no-...\" there must be one real --no- in the first\ncomplete listing even if it's not from the original struct option.\n\nPS. This could could be made simpler with \";&\" to fall through from\n\"--no-*\" block and share the code but \";&\" is not available on bash-3\n(i.e. Mac)\n\nSigned-off-by: Nguyễn Thái Ngọc Duy <pclouds@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/b221b5ab9b92f3def37184db6e052ec87d7635b4"},{"sha":"e9502c0a7fdb5649e3a3aece4e0d54ddb22983df","author":{"name":"Jeff King","email":"696e3fbcf235d40b6ea1ebd61c87cbea79d444e7@peff.net"},"message":"fetch-pack: don't try to fetch peel values with --all\n\nWhen \"fetch-pack --all\" sees a tag-to-blob on the remote, it\ntries to fetch both the tag itself (\"refs/tags/foo\") and the\npeeled value that the remote advertises (\"refs/tags/foo^{}\").\nAsking for the object pointed to by the latter can cause\nupload-pack to complain with \"not our ref\", since it does\nnot mark the peeled objects with the OUR_REF (unless they\nwere at the tip of some other ref).\n\nArguably upload-pack _should_ be marking those peeled\nobjects. But it never has in the past, since clients would\ngenerally just ask for the tag and expect to get the peeled\nvalue along with it. And that's how \"git fetch\" works, as\nwell as older versions of \"fetch-pack --all\".\n\nThe problem was introduced by 5f0fc64513 (fetch-pack:\neliminate spurious error messages, 2012-09-09). Before then,\nthe matching logic was something like:\n\n  if (refname is ill-formed)\n     do nothing\n  else if (doing --all)\n     always consider it matched\n  else\n     look through list of sought refs for a match\n\nThat commit wanted to flip the order of the second two arms\nof that conditional. But we ended up with:\n\n  if (refname is ill-formed)\n    do nothing\n  else\n    look through list of sought refs for a match\n\n  if (--all and no match so far)\n    always consider it matched\n\nThat means tha an ill-formed ref will trigger the --all\nconditional block, even though we should just be ignoring\nit. We can fix that by having a single \"else\" with all of\nthe well-formed logic, that checks the sought refs and\n\"--all\" in the correct order.\n\nReported-by: Kirill Smelkov <kirr@nexedi.com>\nSigned-off-by: Jeff King <peff@peff.net>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/e9502c0a7fdb5649e3a3aece4e0d54ddb22983df"},{"sha":"cac1137dc4908b03642ee10c45eb687feb9335c1","author":{"name":"Jonathan Tan","email":"a1f160b521cd973a24f632d654869fc52afb36fa@google.com"},"message":"list-objects: check if filter is NULL before using\n\nIn partial_clone_get_default_filter_spec(), the\ncore_partial_clone_filter_default variable may be NULL; ensure that it\nis not NULL before using it.\n\nSigned-off-by: Jonathan Tan <jonathantanmy@google.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/cac1137dc4908b03642ee10c45eb687feb9335c1"},{"sha":"d067d9888778ae17aae8280c1b662b29c3490bad","author":{"name":"Masaya Suzuki","email":"d03097699fe1654ce6e9a66ebcc23f4e93d8b8da@google.com"},"message":"builtin/send-pack: populate the default configs\n\nbuiltin/send-pack didn't call git_default_config, and because of this\ngit push --signed didn't respect the username and email in gitconfig in\nthe HTTP transport.\n\nSigned-off-by: Masaya Suzuki <masayasuzuki@google.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/d067d9888778ae17aae8280c1b662b29c3490bad"},{"sha":"c12c9df5275add49b7b47cad82879a84c6bea469","author":{"name":"Kirill Smelkov","email":"b0eeaac46e675e9f95bf68c0df1041cf581c26f4@nexedi.com"},"message":"fetch-pack: test explicitly that --all can fetch tag references pointing to non-commits\n\nFetch-pack --all became broken with respect to unusual tags in\n5f0fc64513 (fetch-pack: eliminate spurious error messages, 2012-09-09),\nand was fixed only recently in e9502c0a7f (fetch-pack: don't try to fetch\npeel values with --all, 2018-06-11). However the test added in\ne9502c0a7f does not explicitly cover all funky cases.\n\nIn order to be sure fetching funky tags will never break, let's\nexplicitly test all relevant cases with 4 tag objects pointing to 1) a\nblob, 2) a tree, 3) a commit, and 4) another tag objects. The referenced\ntag objects themselves are referenced from under regular refs/tags/*\nnamespace. Before e9502c0a7f `fetch-pack --all` was failing e.g. this way:\n\n        .../git/t/trash directory.t5500-fetch-pack/fetchall$ git ls-remote ..\n        44085874...        HEAD\n        ...\n        bc4e9e1f...        refs/tags/tag-to-blob\n        038f48ad...        refs/tags/tag-to-blob^{}\t# peeled\n        520db1f5...        refs/tags/tag-to-tree\n        7395c100...        refs/tags/tag-to-tree^{}\t# peeled\n\n        .../git/t/trash directory.t5500-fetch-pack/fetchall$ git fetch-pack --all ..\n        fatal: A git upload-pack: not our ref 038f48ad...\n        fatal: The remote end hung up unexpectedly\n\nHelped-by: Junio C Hamano <gitster@pobox.com>\nSigned-off-by: Kirill Smelkov <kirr@nexedi.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/c12c9df5275add49b7b47cad82879a84c6bea469"},{"sha":"5fc84755f1478ea8c0f05b8d7be67a3c96a24bff","author":{"name":"Stefan Beller","email":"a7f3b1612c245dae606b3b9617b4f52187fddb65@google.com"},"message":"submodule: fix NULL correctness in renamed broken submodules\n\nWhen fetching with recursing into submodules, the fetch logic inspects\nthe superproject which submodules actually need to be fetched. This is\ntricky for submodules that were renamed in the fetched range of commits.\nThis was implemented in c68f8375760 (implement fetching of moved\nsubmodules, 2017-10-16), and this patch fixes a mistake in the logic\nthere.\n\nWhen the warning is printed, the `name` might be NULL as\ndefault_name_or_path can return NULL, so fix the warning to use the path\nas obtained from the diff machinery, as that is not NULL.\n\nWhile at it, make sure we only attempt to load the submodule if a git\ndirectory of the submodule is found as default_name_or_path will return\nNULL in case the git directory cannot be found. Note that passing NULL\nto submodule_from_name is just a semantic error, as submodule_from_name\naccepts NULL as a value, but then the return value is not the submodule\nthat was asked for, but some arbitrary other submodule. (Cf. 'config_from'\nin submodule-config.c: \"If any parameter except the cache is a NULL\npointer just return the first submodule. Can be used to check whether\nthere are any submodules parsed.\")\n\nReported-by: Duy Nguyen <pclouds@gmail.com>\nHelped-by: Duy Nguyen <pclouds@gmail.com>\nHelped-by: Heiko Voigt <hvoigt@hvoigt.net>\nSigned-off-by: Stefan Beller <sbeller@google.com>\nAcked-by: Heiko Voigt <hvoigt@hvoigt.net>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/5fc84755f1478ea8c0f05b8d7be67a3c96a24bff"},{"sha":"c3749f6e597a7b8140181fa5efc95f3f08595f8c","author":{"name":"Stefan Beller","email":"a7f3b1612c245dae606b3b9617b4f52187fddb65@google.com"},"message":"t5526: test recursive submodules when fetching moved submodules\n\nThe topic merged in 0c7ecb7c311 (Merge branch 'sb/submodule-move-nested',\n2018-05-08) provided support for moving nested submodules.\n\nRemove the NEEDSWORK comment and implement the nested submodules test as\nthe comment hinted at.\n\nSigned-off-by: Stefan Beller <sbeller@google.com>\nAcked-by: Heiko Voigt <hvoigt@hvoigt.net>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/c3749f6e597a7b8140181fa5efc95f3f08595f8c"},{"sha":"037714252f74ae77e816018e43b2504a1b057246","author":{"name":"Junio C Hamano","email":"a6723cc3f76163bf7adb636a73ac3b0ceb3e6b9b@pobox.com"},"message":"tests: clean after SANITY tests\n\nSome of our tests try to make sure Git behaves sensibly in a\nread-only directory, by dropping 'w' permission bit before doing a\ntest and then restoring it after it is done.  The latter is needed\nfor the test framework to clean after itself without leaving a\nleftover directory that cannot be removed.\n\nAncient parts of tests however arrange the above with\n\n\tchmod a-w . &&\n\t... do the test ...\n\tstatus=$?\n\tchmod 775 .\n\t(exit $status)\n\nwhich obviously would not work if the test somehow dies before it\nhas the chance to do \"chmod 775\".  Rewrite them by following a more\nrobust pattern recently written tests use, which is\n\n\ttest_when_finished \"chmod 775 .\" &&\n\tchmod a-w . &&\n\t... do the test ...\n\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/037714252f74ae77e816018e43b2504a1b057246"},{"sha":"94a2bb56b34eaed77a6d21962999716c2104be1a","author":{"name":"Todd Zullinger","email":"ef20ee0e31e0ea2e6153df3c6a7c131757c7c986@pobox.com"},"message":"git-credential-netrc: minor whitespace cleanup in test script\n\nSigned-off-by: Todd Zullinger <tmz@pobox.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/94a2bb56b34eaed77a6d21962999716c2104be1a"},{"sha":"04f673d7e47ba8aa413a47038abfc76b16d6c23b","author":{"name":"Luis Marsano","email":"64ff3bd41563dc3ff33fa823e0dbef82de156dc3@gmail.com"},"message":"git-credential-netrc: use in-tree Git.pm for tests\n\nThe netrc test.pl script calls git-credential-netrc which imports the\nGit module.  Pass GITPERLLIB to git-credential-netrc via PERL5LIB to\nensure the in-tree Git module is used for testing.\n\nSigned-off-by: Luis Marsano <luis.marsano@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/04f673d7e47ba8aa413a47038abfc76b16d6c23b"},{"sha":"9347166d5d4a07d20e32f45b92435bb788425f1e","author":{"name":"Luis Marsano","email":"64ff3bd41563dc3ff33fa823e0dbef82de156dc3@gmail.com"},"message":"git-credential-netrc: fix exit status when tests fail\n\nSigned-off-by: Luis Marsano <luis.marsano@gmail.com>\nSigned-off-by: Junio C Hamano <gitster@pobox.com>","distinct":false,"url":"https://api.github.com/repos/peff/git/commits/9347166d5d4a07d20e32f45b92435bb788425f1e"}]}
{"actor":{"display_login":"peff"}}