summaryrefslogtreecommitdiff
path: root/tests/libgit2/refs
Commit message (Collapse)AuthorAgeFilesLines
* sha256: wrap_odb supports SHA256Edward Thomson2023-05-061-1/+2
|
* Fix parsing rev with reflog of HEAD (e.g., HEAD@{3})Sven Strickroth2023-02-141-0/+3
| | | | | | Fixes issue #6156. Signed-off-by: Sven Strickroth <email@cs-ware.de>
* sha256: indirection for experimental functionsEdward Thomson2022-07-1315-55/+56
| | | | | The experimental function signature is only available when `GIT_EXPERIMENTAL_SHA256` is enabled.
* Merge pull request #6191 from libgit2/ethomson/sha256_pocEdward Thomson2022-07-1317-80/+80
|\ | | | | RFC: SHA256 proof of concept
| * odb: add git_odb_optionsEdward Thomson2022-06-201-1/+1
| | | | | | | | | | Users will need to be able to specify the object id type for the given object database; add a new `git_odb_options` with that option.
| * oid: give oids a typeEdward Thomson2022-06-2014-54/+54
| | | | | | | | | | `git_oid`s now have a type, and we require the oid type when creating the object id from creation functions.
| * object: move oid header printing to objectEdward Thomson2022-06-141-8/+8
| |
| * oid: define GIT_OID_SHA1_ZEROEdward Thomson2022-06-144-8/+8
| | | | | | | | | | Callers should not assume the layout of the oid structure; provide them a macro that defines the null / zero sha1 object id.
| * oid: `GIT_OID_*SZ` is now `GIT_OID_SHA1_*SIZE`Edward Thomson2022-06-142-9/+9
| | | | | | | | | | In preparation for SHA256 support, `GIT_OID_RAWSZ` and `GIT_OID_HEXSZ` need to indicate that they're the size of _SHA1_ OIDs.
* | Merge branch 'main' into fix-invalid-branch-nameyuangli2022-07-121-0/+8
|/
* revparse: Remove error-prone, redundant testCarl Dong2022-05-091-2/+0
| | | | | | | | | | | Originally introduced in: 776a6a8e5f8e258d31aded73c0ce38df6ac7bdc4 This test case has recently been fixed in bdab22384cc61d315005a65456a9f9563bb27c8f, but that fix will only last for a year. Next year the same problem will crop up and the test will need to be re-edited. This is not ideal as - This test case becomes an unnecessary burden for developers - Downstream distros or even just users who want to build older versions of libgit2 are guaranteed to have this test fail Furthermore, this test case is entirely unnecessary, as the functionality that was originally (see 776a6a8e5f8e258d31aded73c0ce38df6ac7bdc4) intended to be tested is well-covered by subsequent tests which specify a date instead of a "x ago" specification.
* revparse: adjust reflog test as we move away from the datesCarlos Martín Nieto2022-05-031-1/+1
| | | | | | | | The dates we use in `refs::revparse::date` has just passed the ten years, so now everything is beyond ten years, leading to an unexpected commit being returned. Adjust it to 11 years so it all looks fine again.
* refactor: `tests` is now `tests/libgit2`Edward Thomson2022-02-2244-0/+6743
Like we want to separate libgit2 and utility source code, we want to separate libgit2 and utility tests. Start by moving all the tests into libgit2.