@axosoft/nodegit
Advanced tools
Changelog
<a name="v0-25-0-alpha-7" href="#v0-25-0-alpha-7">v0.25.0-alpha.7</a> (2019-02-20)
Changelog
<a name="v0-25-0-alpha-6" href="#v0-25-0-alpha-6">v0.25.0-alpha.6</a> (2019-02-14)
Changelog
<a name="v0-25-0-alpha-5" href="#v0-25-0-alpha-5">v0.25.0-alpha.5</a> (2019-02-11)
Changelog
<a name="v0-25-0-alpha-4" href="#v0-25-0-alpha-4">v0.25.0-alpha.4</a> (2019-02-08)
HEAD
ref.NodeGit.Signature.default
to async, because it actually ends up reading the config.NodeGit.Oid.fromString
's internal implementation from git_oid_fromstr
to git_oid_fromstrp
NodeGit.Reference.updateTerminal
Changelog
<a name="v0-25-0-alpha-3" href="#v0-25-0-alpha-3">v0.25.0-alpha.3</a> (2019-02-05)
type SigningCallback = (content: string) => {| code: number, field?: string, signedData?: string |};
If the code is NodeGit.Error.CODE.OK
or 0, the operation will succeed and at least signedData is expected to be filled out.
If the code is a negative number, except for NodeGit.Error.CODE.PASSTHROUGH
, the signing operation will fail.
If the code is NodeGit.Error.CODE.PASSTHROUGH
, the operation will continue without signing the object.Changelog
<a name="v0-25-0-alpha-2" href="#v0-25-0-alpha-2">v0.25.0-alpha.2</a> (2019-02-01)
Changelog
<a name="v0-25-0-alpha-1" href="#v0-25-0-alpha-1">v0.25.0-alpha.1</a> (2019-01-30)
updateRef
parameter to Repository#createCommitWithSignature #1610Changelog
<a name="v0-24-0" href="#v0-24-0">v0.24.0</a> (2019-01-16)
Mostly due to missing support anyway, please report anything you were using as an issue.
fileHistoryWalk
#1583